Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a609e41164ee3f47233a22ac9991de4fa650537b78a4a7a3d25f4d801545a1b1

Tx prefix hash: 2cf379e59fc8676bcdef3cc4789007a3bfe2221a768b769f010aa688ca588c47
Tx public key: 8a3a11a55d55aa511a3fdb7bdb56c324a110f1788074251612b4f2f3ea63247d
Timestamp: 1764720848 Timestamp [UCT]: 2025-12-03 00:14:08 Age [y:d:h:m:s]: 00:001:02:36:02
Block: 1425185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 789 RingCT/type: yes/0
Extra: 018a3a11a55d55aa511a3fdb7bdb56c324a110f1788074251612b4f2f3ea63247d0211000000044e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fb61a93833ca9eab44b5ed36f5cdfd3a0d0504be3415612eeb241dc36c9cc27 0.600000000000 1913818 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": 1425195, "vin": [ { "gen": { "height": 1425185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fb61a93833ca9eab44b5ed36f5cdfd3a0d0504be3415612eeb241dc36c9cc27" } } ], "extra": [ 1, 138, 58, 17, 165, 93, 85, 170, 81, 26, 63, 219, 123, 219, 86, 195, 36, 161, 16, 241, 120, 128, 116, 37, 22, 18, 180, 242, 243, 234, 99, 36, 125, 2, 17, 0, 0, 0, 4, 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