Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 387da15e13029402700b5156a1bf5ac87c25086a027f94d38534a15036a32cee

Tx prefix hash: f5fbef2c8ce525e3129d75b7d91bbe6c71dc38cc275126109536d1ca9949125d
Tx public key: d9e8a33f3d38870535a2fd5f80d2a6df7184548363cdb1091f8afac210bbe9de
Timestamp: 1645692813 Timestamp [UCT]: 2022-02-24 08:53:33 Age [y:d:h:m:s]: 02:321:02:59:31
Block: 445385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 748911 RingCT/type: yes/0
Extra: 01d9e8a33f3d38870535a2fd5f80d2a6df7184548363cdb1091f8afac210bbe9de02110000001c5eb576c5000000000000000000

1 output(s) for total of 20.523663828000 dcy

stealth address amount amount idx
00: 06760ae7e515acbc22572190c1d36a2ef0ac757867e717e4f07fd5890bc912f2 20.523663828000 858960 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": 445395, "vin": [ { "gen": { "height": 445385 } } ], "vout": [ { "amount": 20523663828, "target": { "key": "06760ae7e515acbc22572190c1d36a2ef0ac757867e717e4f07fd5890bc912f2" } } ], "extra": [ 1, 217, 232, 163, 63, 61, 56, 135, 5, 53, 162, 253, 95, 128, 210, 166, 223, 113, 132, 84, 131, 99, 205, 177, 9, 31, 138, 250, 194, 16, 187, 233, 222, 2, 17, 0, 0, 0, 28, 94, 181, 118, 197, 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