Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ecd333559c059de8816d1b67b9faa6163ebaeaec4f0545f7bb32d519a7f73a9

Tx prefix hash: 02e868d5fef0c4a337de77150444954eed2622ce1550d7525e7da72d362f2089
Tx public key: ee71d205a2f4f2fd9acc841fab84f229f3a6f54ca4743a1e2400ec5b474a2c4d
Timestamp: 1732348988 Timestamp [UCT]: 2024-11-23 08:03:08 Age [y:d:h:m:s]: 00:000:22:42:50
Block: 1159843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 669 RingCT/type: yes/0
Extra: 01ee71d205a2f4f2fd9acc841fab84f229f3a6f54ca4743a1e2400ec5b474a2c4d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6310b28345ddbb86fe3e6b73dbf502fc382ba6680322691db2630251a27091db 0.600000000000 1645482 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": 1159853, "vin": [ { "gen": { "height": 1159843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6310b28345ddbb86fe3e6b73dbf502fc382ba6680322691db2630251a27091db" } } ], "extra": [ 1, 238, 113, 210, 5, 162, 244, 242, 253, 154, 204, 132, 31, 171, 132, 242, 41, 243, 166, 245, 76, 164, 116, 58, 30, 36, 0, 236, 91, 71, 74, 44, 77, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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