Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b929c471607ae61ea77497c5f26c3b266aff4b45bd41ff0d228e057a4718a018

Tx prefix hash: db7f90ec97e4fb2a445f6fd6f48113733fe55bd6fd084f81b1f9fa6b0e492b8e
Tx public key: e11a2a7289b1a233393e6fa546bbcb2dda438c5fc870c5d7191a06459bcc7ed1
Timestamp: 1711796350 Timestamp [UCT]: 2024-03-30 10:59:10 Age [y:d:h:m:s]: 01:011:10:18:43
Block: 989571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269106 RingCT/type: yes/0
Extra: 01e11a2a7289b1a233393e6fa546bbcb2dda438c5fc870c5d7191a06459bcc7ed10211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f50416e16a1ab24c8bed478490f53825e778f162c2a6382f7700542ac3d1c6a 0.600000000000 1449870 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": 989581, "vin": [ { "gen": { "height": 989571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f50416e16a1ab24c8bed478490f53825e778f162c2a6382f7700542ac3d1c6a" } } ], "extra": [ 1, 225, 26, 42, 114, 137, 177, 162, 51, 57, 62, 111, 165, 70, 187, 203, 45, 218, 67, 140, 95, 200, 112, 197, 215, 25, 26, 6, 69, 155, 204, 126, 209, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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