Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 177b244a55bff34fa392b185276c076a6079f01ea1373582c73c5b75883e09fb

Tx prefix hash: a183b3eddea9c94685966690babb6adaf599bcdc72bb8383418f940ab1e59c0f
Tx public key: d38a004b28b07eb65d5d50bbc170bd35c1d3386778de438b984d9fb952e9ce0b
Timestamp: 1704083101 Timestamp [UCT]: 2024-01-01 04:25:01 Age [y:d:h:m:s]: 01:100:23:15:54
Block: 925588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333283 RingCT/type: yes/0
Extra: 01d38a004b28b07eb65d5d50bbc170bd35c1d3386778de438b984d9fb952e9ce0b021100000004ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14fd69c0dcd5b58bfa85f857789a5fc4a16b16e4079ceb53197fc6c96f6b0ad4 0.600000000000 1383352 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": 925598, "vin": [ { "gen": { "height": 925588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14fd69c0dcd5b58bfa85f857789a5fc4a16b16e4079ceb53197fc6c96f6b0ad4" } } ], "extra": [ 1, 211, 138, 0, 75, 40, 176, 126, 182, 93, 93, 80, 187, 193, 112, 189, 53, 193, 211, 56, 103, 120, 222, 67, 139, 152, 77, 159, 185, 82, 233, 206, 11, 2, 17, 0, 0, 0, 4, 172, 50, 141, 17, 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