Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864ef8670676a360b9a89d98469337997fc1a2350467a04e81ce7fd1fb0db0d2

Tx prefix hash: 896edb3138b4df27294e55facdd4a1c30f0e305297aa6bf24cef99381f16fa12
Tx public key: 6dbb3ead17211e855d4070a46868449d15722373cc821beb9a5c8c4c3d3cd8a3
Timestamp: 1724578734 Timestamp [UCT]: 2024-08-25 09:38:54 Age [y:d:h:m:s]: 00:247:06:44:04
Block: 1095512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176617 RingCT/type: yes/0
Extra: 016dbb3ead17211e855d4070a46868449d15722373cc821beb9a5c8c4c3d3cd8a3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b22e0d476e19e619d2974fc19491603acddd0930cde70cace5cfe904c4c7f1b 0.600000000000 1570689 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": 1095522, "vin": [ { "gen": { "height": 1095512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b22e0d476e19e619d2974fc19491603acddd0930cde70cace5cfe904c4c7f1b" } } ], "extra": [ 1, 109, 187, 62, 173, 23, 33, 30, 133, 93, 64, 112, 164, 104, 104, 68, 157, 21, 114, 35, 115, 204, 130, 27, 235, 154, 92, 140, 76, 61, 60, 216, 163, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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