Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb9924e29ceaf57622f70dc95b709f7901f57e235e38521347557285ec6ef76b

Tx prefix hash: 9c8e9b2ee3d91b164f9e013488d9a0c648f23e8475fb053505e23f38ab68cce5
Tx public key: 1e29c4a88d684587dbd5a1ed7e62f0f2cdb3aa661589d93ca54294da3f8b9a97
Timestamp: 1728621239 Timestamp [UCT]: 2024-10-11 04:33:59 Age [y:d:h:m:s]: 00:179:18:57:37
Block: 1129029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128276 RingCT/type: yes/0
Extra: 011e29c4a88d684587dbd5a1ed7e62f0f2cdb3aa661589d93ca54294da3f8b9a9702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f10a9570cccb26846ace77b97e0ce16d261e39d7ee9ff929017153dacb8a760d 0.600000000000 1611852 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": 1129039, "vin": [ { "gen": { "height": 1129029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f10a9570cccb26846ace77b97e0ce16d261e39d7ee9ff929017153dacb8a760d" } } ], "extra": [ 1, 30, 41, 196, 168, 141, 104, 69, 135, 219, 213, 161, 237, 126, 98, 240, 242, 205, 179, 170, 102, 21, 137, 217, 60, 165, 66, 148, 218, 63, 139, 154, 151, 2, 17, 0, 0, 0, 3, 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