Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e675227a43a295971e492c3149cd28c6684b546a80410277f6a194ad597116

Tx prefix hash: c6e7ad7d9d447396bd460df6a2170660d3a66c7318267e5debd3bb3c60e3f554
Tx public key: d77e732075c4155bea67df05088f0ade62d85be3a0f4f313c24aa30610014968
Timestamp: 1736680154 Timestamp [UCT]: 2025-01-12 11:09:14 Age [y:d:h:m:s]: 00:157:13:38:14
Block: 1195697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112311 RingCT/type: yes/0
Extra: 01d77e732075c4155bea67df05088f0ade62d85be3a0f4f313c24aa306100149680211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89b9c1d4e25948fd0237b2cc4c3906cf432b2e47cb65de20e0b98133257d22d5 0.600000000000 1682288 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": 1195707, "vin": [ { "gen": { "height": 1195697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89b9c1d4e25948fd0237b2cc4c3906cf432b2e47cb65de20e0b98133257d22d5" } } ], "extra": [ 1, 215, 126, 115, 32, 117, 196, 21, 91, 234, 103, 223, 5, 8, 143, 10, 222, 98, 216, 91, 227, 160, 244, 243, 19, 194, 74, 163, 6, 16, 1, 73, 104, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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