Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00b20075f0665b90ea660609a1f870d6261d286720b7f12b228dac3ab060abbc

Tx prefix hash: db8df942f6ae8d4933b4ab0ded1ca46f94c715d155c7824e7bc66a75c49fb9f3
Tx public key: 62e627f268d0378a48ea260f4b0348ba9c23b251ea55e88e110cd542b7a75334
Timestamp: 1732452695 Timestamp [UCT]: 2024-11-24 12:51:35 Age [y:d:h:m:s]: 00:199:23:31:39
Block: 1160698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142745 RingCT/type: yes/0
Extra: 0162e627f268d0378a48ea260f4b0348ba9c23b251ea55e88e110cd542b7a7533402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4cc5a584f56d9bc2be7c998ecbd3562cc5bf3d37c400d34eed25f2e8bb469d2 0.600000000000 1646347 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": 1160708, "vin": [ { "gen": { "height": 1160698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4cc5a584f56d9bc2be7c998ecbd3562cc5bf3d37c400d34eed25f2e8bb469d2" } } ], "extra": [ 1, 98, 230, 39, 242, 104, 208, 55, 138, 72, 234, 38, 15, 75, 3, 72, 186, 156, 35, 178, 81, 234, 85, 232, 142, 17, 12, 213, 66, 183, 167, 83, 52, 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