Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 503abf8fa55bebd48165f07108eebd5aec93d10c04891e32055f6e3bddadf1f0

Tx prefix hash: d8143ab3dcf158c3a4be6abe41d467d3caf10e87cf3f826d6e183fe81d63eaca
Tx public key: 96c1aa4d926bdad2a60eb914ad1ac67e01078accd819cbe6b773d426035a0285
Timestamp: 1751578182 Timestamp [UCT]: 2025-07-03 21:29:42 Age [y:d:h:m:s]: 00:139:07:19:28
Block: 1318184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97828 RingCT/type: yes/0
Extra: 0196c1aa4d926bdad2a60eb914ad1ac67e01078accd819cbe6b773d426035a0285021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2acb4d404c2d16943d97f1aea93f006b262ea8db3bae561671f846b32446f4a 0.600000000000 1805859 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": 1318194, "vin": [ { "gen": { "height": 1318184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2acb4d404c2d16943d97f1aea93f006b262ea8db3bae561671f846b32446f4a" } } ], "extra": [ 1, 150, 193, 170, 77, 146, 107, 218, 210, 166, 14, 185, 20, 173, 26, 198, 126, 1, 7, 138, 204, 216, 25, 203, 230, 183, 115, 212, 38, 3, 90, 2, 133, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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