Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f602b89de5285c55d34eb2d2c307d8f9d991917e088bdcf432088cbfdb986e9

Tx prefix hash: 224b05ab2b502f17cdf2eb5b374f241521013088bd4fdff1bca126c62f148194
Tx public key: 86ad3be992738f8676ac9c3c954ebccbd2c45a12deaf57f522c1b8f2e294dc3d
Timestamp: 1731005511 Timestamp [UCT]: 2024-11-07 18:51:51 Age [y:d:h:m:s]: 00:150:22:24:48
Block: 1148717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107683 RingCT/type: yes/0
Extra: 0186ad3be992738f8676ac9c3c954ebccbd2c45a12deaf57f522c1b8f2e294dc3d02110000000901491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fceddcf0674c53262d9e10afff11593e98b9efdb9846581716c3cbc000d6ce60 0.600000000000 1633630 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": 1148727, "vin": [ { "gen": { "height": 1148717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fceddcf0674c53262d9e10afff11593e98b9efdb9846581716c3cbc000d6ce60" } } ], "extra": [ 1, 134, 173, 59, 233, 146, 115, 143, 134, 118, 172, 156, 60, 149, 78, 188, 203, 210, 196, 90, 18, 222, 175, 87, 245, 34, 193, 184, 242, 226, 148, 220, 61, 2, 17, 0, 0, 0, 9, 1, 73, 31, 136, 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