Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0219c6df8c0023c75f92f2d822a73c90c7dbfb7106c70c6c1dbefc48cf07016

Tx prefix hash: 66848489bf11a3e5920a60ed0a8e7f735d1d04f1c3fd46eda39c266fa99a7292
Tx public key: 18fae7eebdef3dc84ca96dd20ee6e157d06bbdf77fd179e378023af4439eb11e
Timestamp: 1702650563 Timestamp [UCT]: 2023-12-15 14:29:23 Age [y:d:h:m:s]: 01:147:04:50:09
Block: 913719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366357 RingCT/type: yes/0
Extra: 0118fae7eebdef3dc84ca96dd20ee6e157d06bbdf77fd179e378023af4439eb11e02110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ec29e4dc22922c405ec226130325c4c917dd17a042d6ca6719a35d3c77bf98f 0.600000000000 1370995 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": 913729, "vin": [ { "gen": { "height": 913719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ec29e4dc22922c405ec226130325c4c917dd17a042d6ca6719a35d3c77bf98f" } } ], "extra": [ 1, 24, 250, 231, 238, 189, 239, 61, 200, 76, 169, 109, 210, 14, 230, 225, 87, 208, 107, 189, 247, 127, 209, 121, 227, 120, 2, 58, 244, 67, 158, 177, 30, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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