Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f9eb167a87bf512e4b70dd3ab116e4e05e612aa7dc5980462548839902c495a

Tx prefix hash: faf21f9904254a9fad17ffbece3bc65d4703e6d3096ff08f136d583980d836d6
Tx public key: 3f56d4606f6554f3cc62e700bfc0fb16cdabfc7211b76a32f93c69baa5ce969e
Timestamp: 1581239654 Timestamp [UCT]: 2020-02-09 09:14:14 Age [y:d:h:m:s]: 04:319:03:56:32
Block: 61160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120325 RingCT/type: yes/0
Extra: 013f56d4606f6554f3cc62e700bfc0fb16cdabfc7211b76a32f93c69baa5ce969e02110000008b724f989b000000000000000000

1 output(s) for total of 384.903932212000 dcy

stealth address amount amount idx
00: edfae122494a77672e045d15543ce5cb1bcd5d2476fb94b1952f2943b50bd1a0 384.903932212000 112709 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": 61170, "vin": [ { "gen": { "height": 61160 } } ], "vout": [ { "amount": 384903932212, "target": { "key": "edfae122494a77672e045d15543ce5cb1bcd5d2476fb94b1952f2943b50bd1a0" } } ], "extra": [ 1, 63, 86, 212, 96, 111, 101, 84, 243, 204, 98, 231, 0, 191, 192, 251, 22, 205, 171, 252, 114, 17, 183, 106, 50, 249, 60, 105, 186, 165, 206, 150, 158, 2, 17, 0, 0, 0, 139, 114, 79, 152, 155, 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