Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaefd03da8423304a0d7f3629d44cea3cea9c9737d9121c8da87560b75b1c843

Tx prefix hash: 6dbcf8bfdf9f7043086041ad6a13cb1c10322e59d8ff00b295bc99d1f479d326
Tx public key: 0990afdee7c4aa128f1f426c1e11b5e5de340129ebb1f53c1ab1d5d64516efff
Timestamp: 1748911840 Timestamp [UCT]: 2025-06-03 00:50:40 Age [y:d:h:m:s]: 00:162:09:00:56
Block: 1296705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113727 RingCT/type: yes/0
Extra: 010990afdee7c4aa128f1f426c1e11b5e5de340129ebb1f53c1ab1d5d64516efff02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95d69ebdaebe222a41331e6fdff6bfb413d5b928d3afde9a6d50877a33f17cbb 0.600000000000 1784218 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": 1296715, "vin": [ { "gen": { "height": 1296705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95d69ebdaebe222a41331e6fdff6bfb413d5b928d3afde9a6d50877a33f17cbb" } } ], "extra": [ 1, 9, 144, 175, 222, 231, 196, 170, 18, 143, 31, 66, 108, 30, 17, 181, 229, 222, 52, 1, 41, 235, 177, 245, 60, 26, 177, 213, 214, 69, 22, 239, 255, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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