Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9678042fac07eaa0fe04c61f46080b272ad5ef125ffd840f88de341aa107e0c7

Tx prefix hash: d6df251c39527615583920204bbc194841b89082f965968dbf2f9b87e6ca4b2e
Tx public key: 822675dd15a35f971c62c753e93a65aa732c1591d34adaf39072718c6b2f5f68
Timestamp: 1704845816 Timestamp [UCT]: 2024-01-10 00:16:56 Age [y:d:h:m:s]: 01:081:13:44:47
Block: 931904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319404 RingCT/type: yes/0
Extra: 01822675dd15a35f971c62c753e93a65aa732c1591d34adaf39072718c6b2f5f6802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cd2ecd06b8f455dfba1eb449aa48d90bf60c5b565c60617516bb09ffdfda3ee 0.600000000000 1389810 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 931914, "vin": [ { "gen": { "height": 931904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cd2ecd06b8f455dfba1eb449aa48d90bf60c5b565c60617516bb09ffdfda3ee" } } ], "extra": [ 1, 130, 38, 117, 221, 21, 163, 95, 151, 28, 98, 199, 83, 233, 58, 101, 170, 115, 44, 21, 145, 211, 74, 218, 243, 144, 114, 113, 140, 107, 47, 95, 104, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8