Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3c26f3bb2b68d8be168a53b331d166728c3cdb3dc2478e95c0687ce3b7e2169

Tx prefix hash: 2f4fbb95f67822e342ba25e8b43551f83f403d0ded14bac1755f80c43651c9d5
Tx public key: 4bfc7247d7eca283b6cfa3875d1cfc76a6f856a8d2deff6175b742ee5c679410
Timestamp: 1732560583 Timestamp [UCT]: 2024-11-25 18:49:43 Age [y:d:h:m:s]: 00:168:06:41:49
Block: 1161590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120104 RingCT/type: yes/0
Extra: 014bfc7247d7eca283b6cfa3875d1cfc76a6f856a8d2deff6175b742ee5c679410021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33c7df9004775d6b98711c14ba638eb9f780896e19173d3bb262797dc0284f68 0.600000000000 1647245 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": 1161600, "vin": [ { "gen": { "height": 1161590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33c7df9004775d6b98711c14ba638eb9f780896e19173d3bb262797dc0284f68" } } ], "extra": [ 1, 75, 252, 114, 71, 215, 236, 162, 131, 182, 207, 163, 135, 93, 28, 252, 118, 166, 248, 86, 168, 210, 222, 255, 97, 117, 183, 66, 238, 92, 103, 148, 16, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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