Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71729520b02e5d64e659975b8da7ba40262bd3841fa8c5499e440728f388e5e5

Tx prefix hash: 538f0a890bc0d131e3706f8bdc91d77aca5ee8e2a67cc8bb8e68464fee194d96
Tx public key: acf096ec69534be664f36c9d3fac22d636c84bdbacdad2f42a0a3162b1c8d75d
Timestamp: 1577994775 Timestamp [UCT]: 2020-01-02 19:52:55 Age [y:d:h:m:s]: 05:000:20:31:44
Block: 37404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150584 RingCT/type: yes/0
Extra: 01acf096ec69534be664f36c9d3fac22d636c84bdbacdad2f42a0a3162b1c8d75d0211000000684ac5aa02000000000000000000

1 output(s) for total of 461.387550935000 dcy

stealth address amount amount idx
00: a092c5f4c125acc97d224bf303bf24fbda5b00da979e33fbe700b195eaf3d873 461.387550935000 63478 of 0

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": 37414, "vin": [ { "gen": { "height": 37404 } } ], "vout": [ { "amount": 461387550935, "target": { "key": "a092c5f4c125acc97d224bf303bf24fbda5b00da979e33fbe700b195eaf3d873" } } ], "extra": [ 1, 172, 240, 150, 236, 105, 83, 75, 230, 100, 243, 108, 157, 63, 172, 34, 214, 54, 200, 75, 219, 172, 218, 210, 244, 42, 10, 49, 98, 177, 200, 215, 93, 2, 17, 0, 0, 0, 104, 74, 197, 170, 2, 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