Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8e04ccc10e80690d3ffbf2e536caebcf424b9d540f110664716a1dcbf3b4208

Tx prefix hash: 0bf11bd2cd3dd27b9b641e5984eccb0e86928b8500133455ad64484ce377e295
Tx public key: 72b329fd23df7e136ae45d98e8a7c553ee189cd008069d059951a210dc0ea6a3
Timestamp: 1718679428 Timestamp [UCT]: 2024-06-18 02:57:08 Age [y:d:h:m:s]: 00:218:16:22:21
Block: 1046610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156440 RingCT/type: yes/0
Extra: 0172b329fd23df7e136ae45d98e8a7c553ee189cd008069d059951a210dc0ea6a30211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2910bcb39ac4a0e60a8261ac58b19f3322ca9d0831d9dc2c30e1969fbb6a3e91 0.600000000000 1516427 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": 1046620, "vin": [ { "gen": { "height": 1046610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2910bcb39ac4a0e60a8261ac58b19f3322ca9d0831d9dc2c30e1969fbb6a3e91" } } ], "extra": [ 1, 114, 179, 41, 253, 35, 223, 126, 19, 106, 228, 93, 152, 232, 167, 197, 83, 238, 24, 156, 208, 8, 6, 157, 5, 153, 81, 162, 16, 220, 14, 166, 163, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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