Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a637d63dcafa7ae151bd241f5fef59c46812779d7fa41598f230a169ccc36720

Tx prefix hash: 0d4f4ff60f2c7de4c06ca425c2f455c43895e8439a3aaa46b4959b888a47670a
Tx public key: 4b6db1268b66dadcf38769584a7af1b390cb8aa35876df7d34b613e4f62ea2cb
Timestamp: 1759877238 Timestamp [UCT]: 2025-10-07 22:47:18 Age [y:d:h:m:s]: 00:039:00:36:11
Block: 1385028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27959 RingCT/type: yes/0
Extra: 014b6db1268b66dadcf38769584a7af1b390cb8aa35876df7d34b613e4f62ea2cb021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7ccd1142ce28a668fdb1a5565fd97b48d70994b3c98acf091fc99ce5ef42a5e 0.600000000000 1873185 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": 1385038, "vin": [ { "gen": { "height": 1385028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7ccd1142ce28a668fdb1a5565fd97b48d70994b3c98acf091fc99ce5ef42a5e" } } ], "extra": [ 1, 75, 109, 177, 38, 139, 102, 218, 220, 243, 135, 105, 88, 74, 122, 241, 179, 144, 203, 138, 163, 88, 118, 223, 125, 52, 182, 19, 228, 246, 46, 162, 203, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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