Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f930a46b76a542bb84bcd8f8ce5b0778d781ec854575a808b1325303dfc55c

Tx prefix hash: 9e8b37bae9f92ad8022d0b5aa3ad6d9b85259d480081b67db2beb681f6364e58
Tx public key: 1b99bc8a8f5e6f9551c3629a2a69f86255abf34371832bdc24829bf897ed1beb
Timestamp: 1577710776 Timestamp [UCT]: 2019-12-30 12:59:36 Age [y:d:h:m:s]: 05:310:17:12:49
Block: 35033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1369564 RingCT/type: yes/0
Extra: 011b99bc8a8f5e6f9551c3629a2a69f86255abf34371832bdc24829bf897ed1beb02110000000b4ac5aa02000000000000000000

1 output(s) for total of 469.809704064000 dcy

stealth address amount amount idx
00: a6bce17b1a6eaae1bafbed0427b3729a7f81c5b6d9f46c4575c99cc829e0296c 469.809704064000 59018 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": 35043, "vin": [ { "gen": { "height": 35033 } } ], "vout": [ { "amount": 469809704064, "target": { "key": "a6bce17b1a6eaae1bafbed0427b3729a7f81c5b6d9f46c4575c99cc829e0296c" } } ], "extra": [ 1, 27, 153, 188, 138, 143, 94, 111, 149, 81, 195, 98, 154, 42, 105, 248, 98, 85, 171, 243, 67, 113, 131, 43, 220, 36, 130, 155, 248, 151, 237, 27, 235, 2, 17, 0, 0, 0, 11, 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