Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb5aea3cc66ea35d3b3cf53c020567c349f80e8f846351018c9ff26c28e8c9f7

Tx prefix hash: b804e029345a80b3f4d9aa56ae90d62e652833ce251ca10e67af0976453e4dc7
Tx public key: 4a0716d6893f2467ac1c21ad1519bec5d37fc9ca78cf3426300da2cc85d31db6
Timestamp: 1749487109 Timestamp [UCT]: 2025-06-09 16:38:29 Age [y:d:h:m:s]: 00:158:04:01:54
Block: 1301472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110721 RingCT/type: yes/0
Extra: 014a0716d6893f2467ac1c21ad1519bec5d37fc9ca78cf3426300da2cc85d31db602110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 113dcbc77097e94328e78c3de9362e3e4abd029e1435e32d3df28c29bb31f1b3 0.600000000000 1789031 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": 1301482, "vin": [ { "gen": { "height": 1301472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "113dcbc77097e94328e78c3de9362e3e4abd029e1435e32d3df28c29bb31f1b3" } } ], "extra": [ 1, 74, 7, 22, 214, 137, 63, 36, 103, 172, 28, 33, 173, 21, 25, 190, 197, 211, 127, 201, 202, 120, 207, 52, 38, 48, 13, 162, 204, 133, 211, 29, 182, 2, 17, 0, 0, 0, 2, 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