Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 701a562d012a5617ce87ca5cb274e5172d4a91bf6b54014dba90542c20b034e5

Tx prefix hash: 16473b6058cd7c699e51fdd390f9fac6e62cccfe32ff013387eb90a446a8ebbe
Tx public key: 00cd48e8479f82359c2159be02a5d7d04aeb7d1b5a7ef8944afcac3c5d5553ee
Timestamp: 1749726545 Timestamp [UCT]: 2025-06-12 11:09:05 Age [y:d:h:m:s]: 00:151:19:22:04
Block: 1303405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106207 RingCT/type: yes/0
Extra: 0100cd48e8479f82359c2159be02a5d7d04aeb7d1b5a7ef8944afcac3c5d5553ee02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21f2b6ac93b51be5c1cfaac4777b9817141ff45bf7999392caf942a9e66ae021 0.600000000000 1790986 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": 1303415, "vin": [ { "gen": { "height": 1303405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21f2b6ac93b51be5c1cfaac4777b9817141ff45bf7999392caf942a9e66ae021" } } ], "extra": [ 1, 0, 205, 72, 232, 71, 159, 130, 53, 156, 33, 89, 190, 2, 165, 215, 208, 74, 235, 125, 27, 90, 126, 248, 148, 74, 252, 172, 60, 93, 85, 83, 238, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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