Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4405a0d7ad9cbec777b013f13b0eb0f68fbcc8776de0c1ec53c72c4bb8f7bdce

Tx prefix hash: a82db77683ec96d80365165a04c34b2e78ab3c018a2db3dfdcfc324c790a9846
Tx public key: 4fa87e0f45cde14fb4eb4fb2cdf6b110453cd81eb7f6986d2f1227e32bb2bdf9
Timestamp: 1580692312 Timestamp [UCT]: 2020-02-03 01:11:52 Age [y:d:h:m:s]: 05:276:08:54:32
Block: 57403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1347308 RingCT/type: yes/0
Extra: 014fa87e0f45cde14fb4eb4fb2cdf6b110453cd81eb7f6986d2f1227e32bb2bdf902110000000e4943cd9f000000000000000000

1 output(s) for total of 396.107322392000 dcy

stealth address amount amount idx
00: 8c81e3c31a502ae1e8f0a66af37eae2fd93649573f00e23a659b1f7198114ce3 396.107322392000 106098 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": 57413, "vin": [ { "gen": { "height": 57403 } } ], "vout": [ { "amount": 396107322392, "target": { "key": "8c81e3c31a502ae1e8f0a66af37eae2fd93649573f00e23a659b1f7198114ce3" } } ], "extra": [ 1, 79, 168, 126, 15, 69, 205, 225, 79, 180, 235, 79, 178, 205, 246, 177, 16, 69, 60, 216, 30, 183, 246, 152, 109, 47, 18, 39, 227, 43, 178, 189, 249, 2, 17, 0, 0, 0, 14, 73, 67, 205, 159, 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