Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8446d4ba09359ee2a6b87d3707d5d1b444673849bbd915a9dcde574f1125b45

Tx prefix hash: 311bd0982feac4ae738a3a7fc8c276ee0ad53437a151b2783b10efb132b971af
Tx public key: 27727dadd68aed638c4d31ee5b595c954719a44cd5db193fdd3dabe5be3bdf9b
Timestamp: 1708539958 Timestamp [UCT]: 2024-02-21 18:25:58 Age [y:d:h:m:s]: 01:268:00:33:01
Block: 962542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450312 RingCT/type: yes/0
Extra: 0127727dadd68aed638c4d31ee5b595c954719a44cd5db193fdd3dabe5be3bdf9b021100000006cdf2b46b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9337be5986fdf3925bc94d51ef13bf7f060cb37fa947b0c8f3faa1351a724d66 0.600000000000 1422183 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": 962552, "vin": [ { "gen": { "height": 962542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9337be5986fdf3925bc94d51ef13bf7f060cb37fa947b0c8f3faa1351a724d66" } } ], "extra": [ 1, 39, 114, 125, 173, 214, 138, 237, 99, 140, 77, 49, 238, 91, 89, 92, 149, 71, 25, 164, 76, 213, 219, 25, 63, 221, 61, 171, 229, 190, 59, 223, 155, 2, 17, 0, 0, 0, 6, 205, 242, 180, 107, 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