Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e842352f28b3433e71f78bdc5512598e33c56f7dae0a28ef012ce42aa177561

Tx prefix hash: f192d40c46670d4a0e65f36c4a6a02bda9013fa36ba826474b3b2476c5ff2768
Tx public key: 4009c87f1693041ee3f540795efeef6ff1c66b14c3e5def5c02873356c8607df
Timestamp: 1745625227 Timestamp [UCT]: 2025-04-25 23:53:47 Age [y:d:h:m:s]: 00:011:13:43:52
Block: 1269463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8307 RingCT/type: yes/0
Extra: 014009c87f1693041ee3f540795efeef6ff1c66b14c3e5def5c02873356c8607df0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aad39bf9dc3af56e8a35dfca560e4230c0728991a293fa885e16b1ea444c060b 0.600000000000 1756702 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": 1269473, "vin": [ { "gen": { "height": 1269463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aad39bf9dc3af56e8a35dfca560e4230c0728991a293fa885e16b1ea444c060b" } } ], "extra": [ 1, 64, 9, 200, 127, 22, 147, 4, 30, 227, 245, 64, 121, 94, 254, 239, 111, 241, 198, 107, 20, 195, 229, 222, 245, 192, 40, 115, 53, 108, 134, 7, 223, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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