Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 466bd3cbdcf4a61ef9185b29d44d16b6c7570b939386fe19cac92faec77671c8

Tx prefix hash: 39cd1c0a235d1a7b38b217acd47aca01bc4df647d8ccd54d977809da48685489
Tx public key: a84a2b4f965ea51c52735d5f73930b05ee9e06e8ed623d8e5356d38fb6fc13e1
Timestamp: 1733331275 Timestamp [UCT]: 2024-12-04 16:54:35 Age [y:d:h:m:s]: 00:334:08:17:37
Block: 1167969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236481 RingCT/type: yes/0
Extra: 01a84a2b4f965ea51c52735d5f73930b05ee9e06e8ed623d8e5356d38fb6fc13e10211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0536181110dc4e400cfd24f7d1da84e23257d3461be65e74844cae88cce3a859 0.600000000000 1653674 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": 1167979, "vin": [ { "gen": { "height": 1167969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0536181110dc4e400cfd24f7d1da84e23257d3461be65e74844cae88cce3a859" } } ], "extra": [ 1, 168, 74, 43, 79, 150, 94, 165, 28, 82, 115, 93, 95, 115, 147, 11, 5, 238, 158, 6, 232, 237, 98, 61, 142, 83, 86, 211, 143, 182, 252, 19, 225, 2, 17, 0, 0, 0, 5, 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