Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88a009322acb81397ba84ec5b44e731181d2ebf2b9eca91f8b18b4f53c120367

Tx prefix hash: fd73362ae6b12b5add490441d70d8b73c74fe678ddd33083c8df7c055d6ae878
Tx public key: b2777d45a4d828f94be098ecd65c86388a0fcb086264f130f2eb6c660cfe0ea8
Timestamp: 1709144999 Timestamp [UCT]: 2024-02-28 18:29:59 Age [y:d:h:m:s]: 01:042:05:26:40
Block: 967569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291182 RingCT/type: yes/0
Extra: 01b2777d45a4d828f94be098ecd65c86388a0fcb086264f130f2eb6c660cfe0ea802110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a31accb0dcc15009161d9bca4e0f17b64781489fad821ee17b19a0b41d47b0b8 0.600000000000 1427352 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": 967579, "vin": [ { "gen": { "height": 967569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a31accb0dcc15009161d9bca4e0f17b64781489fad821ee17b19a0b41d47b0b8" } } ], "extra": [ 1, 178, 119, 125, 69, 164, 216, 40, 249, 75, 224, 152, 236, 214, 92, 134, 56, 138, 15, 203, 8, 98, 100, 241, 48, 242, 235, 108, 102, 12, 254, 14, 168, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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