Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 548ce099e86d3406fadb3ffd27e25609b5397c01113d57f7a770a35c04fdcfd9

Tx prefix hash: 145eef73b9bedd79078c4f9058f7ef1f75088d3d8b7c18f9d12352c9c5361896
Tx public key: 5a6cca8648c24fa4c4de34c5fd35311d2121dd6050ff10211a311de3d547dff4
Timestamp: 1709939842 Timestamp [UCT]: 2024-03-08 23:17:22 Age [y:d:h:m:s]: 00:353:07:00:44
Block: 974161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252580 RingCT/type: yes/0
Extra: 015a6cca8648c24fa4c4de34c5fd35311d2121dd6050ff10211a311de3d547dff402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4d267c81f7fa7acca71e7ec70752305bbb2dc061b9e33e7ca031d89da7078d4 0.600000000000 1434112 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": 974171, "vin": [ { "gen": { "height": 974161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4d267c81f7fa7acca71e7ec70752305bbb2dc061b9e33e7ca031d89da7078d4" } } ], "extra": [ 1, 90, 108, 202, 134, 72, 194, 79, 164, 196, 222, 52, 197, 253, 53, 49, 29, 33, 33, 221, 96, 80, 255, 16, 33, 26, 49, 29, 227, 213, 71, 223, 244, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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