Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e89b95e66daab90424bcc87ef00eb92f764c5dfc0a957cb85f3e33f18781ccb

Tx prefix hash: eea3cf856081c80b260d9c8b15d0415cdc3a190723ec39983edb4e9c1d07177a
Tx public key: 2b0e299df466744d9f8725d71e452511e8d975bf857738716c9cdf405722a567
Timestamp: 1722419448 Timestamp [UCT]: 2024-07-31 09:50:48 Age [y:d:h:m:s]: 00:084:18:27:53
Block: 1077609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60692 RingCT/type: yes/0
Extra: 012b0e299df466744d9f8725d71e452511e8d975bf857738716c9cdf405722a56702110000000191e13c04000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: ca3f3ef9326a4872e35e24aecad731408f35c9eb92861765eb96fad60752f4a4 0.600010000000 1550162 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": 1077619, "vin": [ { "gen": { "height": 1077609 } } ], "vout": [ { "amount": 600010000, "target": { "key": "ca3f3ef9326a4872e35e24aecad731408f35c9eb92861765eb96fad60752f4a4" } } ], "extra": [ 1, 43, 14, 41, 157, 244, 102, 116, 77, 159, 135, 37, 215, 30, 69, 37, 17, 232, 217, 117, 191, 133, 119, 56, 113, 108, 156, 223, 64, 87, 34, 165, 103, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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