Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54e87029859bb50acf4c63e424fcf9489cb114f73126c049c0ea40868af2de78

Tx prefix hash: 936568372b0a787a418c9d2f5466c49f6c309aa8f1eb7eb6652b8ca77b696fb5
Tx public key: a128fe9b5ea93cb0f56ef26589e880eb36efa373274b09d7001c048a1d8575e6
Timestamp: 1712808459 Timestamp [UCT]: 2024-04-11 04:07:39 Age [y:d:h:m:s]: 01:207:08:55:29
Block: 997907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406893 RingCT/type: yes/0
Extra: 01a128fe9b5ea93cb0f56ef26589e880eb36efa373274b09d7001c048a1d8575e602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c61e25a8b26846ea6b4ba348cd39223e8b6cc5143cd6b2225b7556f806c145eb 0.600000000000 1458341 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": 997917, "vin": [ { "gen": { "height": 997907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c61e25a8b26846ea6b4ba348cd39223e8b6cc5143cd6b2225b7556f806c145eb" } } ], "extra": [ 1, 161, 40, 254, 155, 94, 169, 60, 176, 245, 110, 242, 101, 137, 232, 128, 235, 54, 239, 163, 115, 39, 75, 9, 215, 0, 28, 4, 138, 29, 133, 117, 230, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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