Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c33fad27d8dbfea241256bad25ca6bc2078102a4153456f2aa41cf7d88461235

Tx prefix hash: 7d2cfc780f859be9316e30f7ad62b9a556f0edc6f404a46dae8fbd45cf4a61bd
Tx public key: a55fb085dcdb7dba73a06b5fd88e8af351bd8e6e583d68fd9c68c9e464587cd1
Timestamp: 1714257090 Timestamp [UCT]: 2024-04-27 22:31:30 Age [y:d:h:m:s]: 00:256:03:38:44
Block: 1009939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183345 RingCT/type: yes/0
Extra: 01a55fb085dcdb7dba73a06b5fd88e8af351bd8e6e583d68fd9c68c9e464587cd102110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad7ecab56abe0dc2a117611b6d25175d91a25decc250a60439ceba8a4b84a9a 0.600000000000 1471753 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": 1009949, "vin": [ { "gen": { "height": 1009939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad7ecab56abe0dc2a117611b6d25175d91a25decc250a60439ceba8a4b84a9a" } } ], "extra": [ 1, 165, 95, 176, 133, 220, 219, 125, 186, 115, 160, 107, 95, 216, 142, 138, 243, 81, 189, 142, 110, 88, 61, 104, 253, 156, 104, 201, 228, 100, 88, 124, 209, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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