Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7d081e24af1f508212908be4ca781465c751d3c2a9e10e67dad4783b461084f

Tx prefix hash: f7aa5545b6b3932d59528cc5e8f6de604f57f46e3501f70204c1a03489b6d8a8
Tx public key: 88abe14fe8dfec6f44a566b301739659393d7e6f47587fdc8edf46fb6d01909c
Timestamp: 1702551906 Timestamp [UCT]: 2023-12-14 11:05:06 Age [y:d:h:m:s]: 01:124:16:56:41
Block: 912896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350271 RingCT/type: yes/0
Extra: 0188abe14fe8dfec6f44a566b301739659393d7e6f47587fdc8edf46fb6d01909c02110000000933af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76c40b0e54332b48f47af61c63f5c9a33a2c063883536e2daa54b9d41f81ab05 0.600000000000 1370132 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": 912906, "vin": [ { "gen": { "height": 912896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76c40b0e54332b48f47af61c63f5c9a33a2c063883536e2daa54b9d41f81ab05" } } ], "extra": [ 1, 136, 171, 225, 79, 232, 223, 236, 111, 68, 165, 102, 179, 1, 115, 150, 89, 57, 61, 126, 111, 71, 88, 127, 220, 142, 223, 70, 251, 109, 1, 144, 156, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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