Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b36ce3ac72220ece9dde3cf31375f6c89b1c3ba7b8b8ea97b7dbb79bced735d

Tx prefix hash: be052fdccb8d6440cc88da4687bc2572656e48785dbf0574c69ee749df7ef2d6
Tx public key: cbce354ac5cac3247b6a46a0c82b0700eee4370f9b78bd0f8ff958436f19447d
Timestamp: 1577144068 Timestamp [UCT]: 2019-12-23 23:34:28 Age [y:d:h:m:s]: 05:110:05:46:29
Block: 30189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1228730 RingCT/type: yes/0
Extra: 01cbce354ac5cac3247b6a46a0c82b0700eee4370f9b78bd0f8ff958436f19447d0211000000114fb58672000000000000000000

1 output(s) for total of 487.552393139000 dcy

stealth address amount amount idx
00: 055c7e63c88fcf31490ba122f7cb9ef9519955245c854abfed0c8a20377918d1 487.552393139000 49845 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": 30199, "vin": [ { "gen": { "height": 30189 } } ], "vout": [ { "amount": 487552393139, "target": { "key": "055c7e63c88fcf31490ba122f7cb9ef9519955245c854abfed0c8a20377918d1" } } ], "extra": [ 1, 203, 206, 53, 74, 197, 202, 195, 36, 123, 106, 70, 160, 200, 43, 7, 0, 238, 228, 55, 15, 155, 120, 189, 15, 143, 249, 88, 67, 111, 25, 68, 125, 2, 17, 0, 0, 0, 17, 79, 181, 134, 114, 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