Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 677571a467acb609c13b8176b9a9406be74170b56216fc3d115701a1ede6051e

Tx prefix hash: de61447d87cb58405196de99431b92069430fd4b94524190f3590c2bf6763d4a
Tx public key: 03cbb6c4d9d2cfd27169e6e0b9e08b5858d088b647f0d553880f350ff8ce040b
Timestamp: 1723174084 Timestamp [UCT]: 2024-08-09 03:28:04 Age [y:d:h:m:s]: 01:092:21:16:19
Block: 1083865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324865 RingCT/type: yes/0
Extra: 0103cbb6c4d9d2cfd27169e6e0b9e08b5858d088b647f0d553880f350ff8ce040b02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d722a20886eb550a4a8f5fa0c2afe42cd924835ef1a7a27a31ac548a8a0f18f 0.600000000000 1557940 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": 1083875, "vin": [ { "gen": { "height": 1083865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d722a20886eb550a4a8f5fa0c2afe42cd924835ef1a7a27a31ac548a8a0f18f" } } ], "extra": [ 1, 3, 203, 182, 196, 217, 210, 207, 210, 113, 105, 230, 224, 185, 224, 139, 88, 88, 208, 136, 182, 71, 240, 213, 83, 136, 15, 53, 15, 248, 206, 4, 11, 2, 17, 0, 0, 0, 5, 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