Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1473e13e291a1703adcab99da862e08055b3d8a4e3004bc6d0c615faab85c20e

Tx prefix hash: 67338545ef33b6e492161e38c1bd7867f915e92c81a8988bacb0d97e046e78e6
Tx public key: 3ce3524d56e1f76df5bc8ec6647d9e4f61133dc3fe99623c35015f444f4f016e
Timestamp: 1722028747 Timestamp [UCT]: 2024-07-26 21:19:07 Age [y:d:h:m:s]: 00:328:04:10:06
Block: 1074367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234364 RingCT/type: yes/0
Extra: 013ce3524d56e1f76df5bc8ec6647d9e4f61133dc3fe99623c35015f444f4f016e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82e9134c4253abe7c7c3b4bc1a5a68ab5816fe6675745eed0f6c936254548836 0.600000000000 1546880 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": 1074377, "vin": [ { "gen": { "height": 1074367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82e9134c4253abe7c7c3b4bc1a5a68ab5816fe6675745eed0f6c936254548836" } } ], "extra": [ 1, 60, 227, 82, 77, 86, 225, 247, 109, 245, 188, 142, 198, 100, 125, 158, 79, 97, 19, 61, 195, 254, 153, 98, 60, 53, 1, 95, 68, 79, 79, 1, 110, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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