Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5646dae97ad9f6ba1598c860410ae0bb6a79e89eefbe66feda5667d804c0dbfd

Tx prefix hash: 1cba2286904f189b74de0b64df1652b96ea0803e101d7e5f12ca23ccc2a506b3
Tx public key: de54454b14a04c18bb96aaca874f09e840b35e2f7c516fba06773780ffcb53ab
Timestamp: 1761460034 Timestamp [UCT]: 2025-10-26 06:27:14 Age [y:d:h:m:s]: 00:059:02:06:08
Block: 1398163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42295 RingCT/type: yes/0
Extra: 01de54454b14a04c18bb96aaca874f09e840b35e2f7c516fba06773780ffcb53ab02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db0a98aae5f03046a164d6ccdc89498f280e95bb2722b400570e15f2f38edb9b 0.600000000000 1886456 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": 1398173, "vin": [ { "gen": { "height": 1398163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db0a98aae5f03046a164d6ccdc89498f280e95bb2722b400570e15f2f38edb9b" } } ], "extra": [ 1, 222, 84, 69, 75, 20, 160, 76, 24, 187, 150, 170, 202, 135, 79, 9, 232, 64, 179, 94, 47, 124, 81, 111, 186, 6, 119, 55, 128, 255, 203, 83, 171, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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