Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e459dd91f1631eb2a42dd0e5eb56c6e10e406a5c06de5323ba0fb82f35f1592

Tx prefix hash: 478d0a68fc7d6e566db2381e277ab885749b5931d06d6404f3edf08eb55e71b8
Tx public key: 401e074e1e226cfb06769933a5a3036fd2c279dc756953033fde6aeef0031c85
Timestamp: 1713991077 Timestamp [UCT]: 2024-04-24 20:37:57 Age [y:d:h:m:s]: 00:251:15:15:52
Block: 1007741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180111 RingCT/type: yes/0
Extra: 01401e074e1e226cfb06769933a5a3036fd2c279dc756953033fde6aeef0031c850211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d715268e25e2fc24a10085b922d2ca621318236c57c3c381173cf43e96d1ce16 0.600000000000 1469177 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": 1007751, "vin": [ { "gen": { "height": 1007741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d715268e25e2fc24a10085b922d2ca621318236c57c3c381173cf43e96d1ce16" } } ], "extra": [ 1, 64, 30, 7, 78, 30, 34, 108, 251, 6, 118, 153, 51, 165, 163, 3, 111, 210, 194, 121, 220, 117, 105, 83, 3, 63, 222, 106, 238, 240, 3, 28, 133, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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