Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d411f6795680331d505c05c923b0b86339a1c7df9cc89e10d95a41b6b32d06f9

Tx prefix hash: 34a4609abac63d0ca23ca83b677fe4da54f793e98c0042de64075f37196c212a
Tx public key: d8d6e2479bbe1cd6a1906c6797be85d2fbdd018abfa2a0e9221624a10c4210c6
Timestamp: 1708644017 Timestamp [UCT]: 2024-02-22 23:20:17 Age [y:d:h:m:s]: 01:089:07:47:53
Block: 963404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324902 RingCT/type: yes/0
Extra: 01d8d6e2479bbe1cd6a1906c6797be85d2fbdd018abfa2a0e9221624a10c4210c602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1ec352f301bedcf112297dfa77c4cdccbd1dc3b96725ba13fd9e3fa140de358 0.600000000000 1423115 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": 963414, "vin": [ { "gen": { "height": 963404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1ec352f301bedcf112297dfa77c4cdccbd1dc3b96725ba13fd9e3fa140de358" } } ], "extra": [ 1, 216, 214, 226, 71, 155, 190, 28, 214, 161, 144, 108, 103, 151, 190, 133, 210, 251, 221, 1, 138, 191, 162, 160, 233, 34, 22, 36, 161, 12, 66, 16, 198, 2, 17, 0, 0, 0, 2, 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