Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc3f9025323f0b4bf63342332c14b267b1254da429d0f3235008fcf7d1f6c3d5

Tx prefix hash: bd2406579faf7211b71bcfcc25a701eada0a40d98e0e34dcfeec28ec9b2771ee
Tx public key: 51f34ae817ad3875f6592d84738597bfdd7e174f666b0ecc75a7ecf3667c2c5e
Timestamp: 1623014646 Timestamp [UCT]: 2021-06-06 21:24:06 Age [y:d:h:m:s]: 03:205:17:02:55
Block: 273460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 911599 RingCT/type: yes/0
Extra: 0151f34ae817ad3875f6592d84738597bfdd7e174f666b0ecc75a7ecf3667c2c5e02110000000823fdb90b000000000000000000

1 output(s) for total of 76.195866900000 dcy

stealth address amount amount idx
00: 087aceedc9207587f3409ed16bd0add8c02e8ee2aa953a207698e6812c3c83de 76.195866900000 573708 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": 273470, "vin": [ { "gen": { "height": 273460 } } ], "vout": [ { "amount": 76195866900, "target": { "key": "087aceedc9207587f3409ed16bd0add8c02e8ee2aa953a207698e6812c3c83de" } } ], "extra": [ 1, 81, 243, 74, 232, 23, 173, 56, 117, 246, 89, 45, 132, 115, 133, 151, 191, 221, 126, 23, 79, 102, 107, 14, 204, 117, 167, 236, 243, 102, 124, 44, 94, 2, 17, 0, 0, 0, 8, 35, 253, 185, 11, 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