Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 004bdb788a44039843edfa3ab781a0980a7c63d4a1747b62e8cc18413e245fc9

Tx prefix hash: 2df5d7467552b8e43b691271a366a9b0dbe7dac4c7bf85eb4afb12756d487d00
Tx public key: e5d3b0085512e80e817894c33c661d42dcfd79c78334b762ba0f087f59d815d6
Timestamp: 1763728902 Timestamp [UCT]: 2025-11-21 12:41:42 Age [y:d:h:m:s]: 00:006:20:52:55
Block: 1416949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4935 RingCT/type: yes/0
Extra: 01e5d3b0085512e80e817894c33c661d42dcfd79c78334b762ba0f087f59d815d602110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5259b041e0aa0d5bfb578a1a3c9df665902fd66d86d2be8fa26ee59f1c0b5223 0.600000000000 1905470 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": 1416959, "vin": [ { "gen": { "height": 1416949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5259b041e0aa0d5bfb578a1a3c9df665902fd66d86d2be8fa26ee59f1c0b5223" } } ], "extra": [ 1, 229, 211, 176, 8, 85, 18, 232, 14, 129, 120, 148, 195, 60, 102, 29, 66, 220, 253, 121, 199, 131, 52, 183, 98, 186, 15, 8, 127, 89, 216, 21, 214, 2, 17, 0, 0, 0, 5, 112, 96, 157, 3, 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