Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d876e18f81992d62bbd62ab33bd3a9e367df18c4448f198f2e1157140738e814

Tx prefix hash: f4f957b3cbee5c63cf663c41346b7caee577f91d0a49cf11dc4f869579207d9f
Tx public key: ce41e3fc1469648dd661dd9a9deb6dac30ae627e660acfab9a38f98cb109b6fc
Timestamp: 1699564762 Timestamp [UCT]: 2023-11-09 21:19:22 Age [y:d:h:m:s]: 01:083:01:40:14
Block: 888139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320524 RingCT/type: yes/0
Extra: 01ce41e3fc1469648dd661dd9a9deb6dac30ae627e660acfab9a38f98cb109b6fc02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.700207583000 dcy

stealth address amount amount idx
00: a5c369f464ce126d47e4b81e9043c4445b53afcd266d4edca709bd05a7a63ecd 0.700207583000 1344062 of 0

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": 888149, "vin": [ { "gen": { "height": 888139 } } ], "vout": [ { "amount": 700207583, "target": { "key": "a5c369f464ce126d47e4b81e9043c4445b53afcd266d4edca709bd05a7a63ecd" } } ], "extra": [ 1, 206, 65, 227, 252, 20, 105, 100, 141, 214, 97, 221, 154, 157, 235, 109, 172, 48, 174, 98, 126, 102, 10, 207, 171, 154, 56, 249, 140, 177, 9, 182, 252, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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