Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b14187edd8c8e75e88042a4ff3c9040058478d97de24a9fded5926f713959bc6

Tx prefix hash: 36d9ddf3b25ad61551d222bc3183e334e2891843327ea8ab54a07553f4803667
Tx public key: c9ea043ea9a7e9f72ac937c8a7e3af4905b384a4630a5c69a37bb25a7d3f37fb
Timestamp: 1763823582 Timestamp [UCT]: 2025-11-22 14:59:42 Age [y:d:h:m:s]: 00:005:02:14:44
Block: 1417743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3664 RingCT/type: yes/0
Extra: 01c9ea043ea9a7e9f72ac937c8a7e3af4905b384a4630a5c69a37bb25a7d3f37fb0211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1ab53106dedb27242f6328bb6ec39c264b8c78fc66ec77afb3e4ea8ef4a90ab 0.600000000000 1906270 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": 1417753, "vin": [ { "gen": { "height": 1417743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1ab53106dedb27242f6328bb6ec39c264b8c78fc66ec77afb3e4ea8ef4a90ab" } } ], "extra": [ 1, 201, 234, 4, 62, 169, 167, 233, 247, 42, 201, 55, 200, 167, 227, 175, 73, 5, 179, 132, 164, 99, 10, 92, 105, 163, 123, 178, 90, 125, 63, 55, 251, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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