Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef8d99de2de3c0113aa680dabde8286ffdf42761739e4d0b4063dfaee439f671

Tx prefix hash: ecff0b182d6c99898bf66311885a3262ee799f78a66863b120a34a63d4875058
Tx public key: aa9e162684bee67bdf26e6bbbb984f1c521c51f5dd728f16a5849569f8aa2b08
Timestamp: 1745011611 Timestamp [UCT]: 2025-04-18 21:26:51 Age [y:d:h:m:s]: 00:282:22:34:00
Block: 1264415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199841 RingCT/type: yes/0
Extra: 01aa9e162684bee67bdf26e6bbbb984f1c521c51f5dd728f16a5849569f8aa2b0802110000000b6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fac88f76421aa105c4e0cf743fb6aa42220a25002a64975927adad5dd856dc5a 0.600000000000 1751612 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": 1264425, "vin": [ { "gen": { "height": 1264415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fac88f76421aa105c4e0cf743fb6aa42220a25002a64975927adad5dd856dc5a" } } ], "extra": [ 1, 170, 158, 22, 38, 132, 190, 230, 123, 223, 38, 230, 187, 187, 152, 79, 28, 82, 28, 81, 245, 221, 114, 143, 22, 165, 132, 149, 105, 248, 170, 43, 8, 2, 17, 0, 0, 0, 11, 108, 152, 170, 61, 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