Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f30fd189622c8b352c7467c12a27a5e91831b1a834664548f1d032166836fdc

Tx prefix hash: c0cbbb0c641dd1802ae1805361181ff1499ea99f8655555db3777d2ebadb5dc8
Tx public key: cc93eb5f73ec4e4a4d9a8a3ec23d2a34d2cf20bfb3451387880df80609a7fe90
Timestamp: 1749905688 Timestamp [UCT]: 2025-06-14 12:54:48 Age [y:d:h:m:s]: 00:160:10:28:09
Block: 1304853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112420 RingCT/type: yes/0
Extra: 01cc93eb5f73ec4e4a4d9a8a3ec23d2a34d2cf20bfb3451387880df80609a7fe90021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d274b779ce5c59ca2afa4176d3626440bccb6abacff545742f10d65fc6a4bb38 0.600000000000 1792446 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": 1304863, "vin": [ { "gen": { "height": 1304853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d274b779ce5c59ca2afa4176d3626440bccb6abacff545742f10d65fc6a4bb38" } } ], "extra": [ 1, 204, 147, 235, 95, 115, 236, 78, 74, 77, 154, 138, 62, 194, 61, 42, 52, 210, 207, 32, 191, 179, 69, 19, 135, 136, 13, 248, 6, 9, 167, 254, 144, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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