Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c43641f0cbdc6a5a10092aed76c5ce94d4a935bdf0fc10dd5bc0906901b19587

Tx prefix hash: a4b973bbcf9f065a9cdad07f2fd429f244f7ce070a347c8a80db9eccc3061286
Tx public key: 772a1ca9fe75b20525e245a86ffebb4431d7d0ac02688b518b99ce8530560ce7
Timestamp: 1698392650 Timestamp [UCT]: 2023-10-27 07:44:10 Age [y:d:h:m:s]: 01:087:20:39:46
Block: 878636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323975 RingCT/type: yes/0
Extra: 01772a1ca9fe75b20525e245a86ffebb4431d7d0ac02688b518b99ce8530560ce702110000000133af99f4000000000000000000

1 output(s) for total of 0.752859973000 dcy

stealth address amount amount idx
00: 701bc6e8e62d10d3d9c77f31d8bf63a84e13bf6cb96c17cbf46f90b708f96a11 0.752859973000 1334098 of 0

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": 878646, "vin": [ { "gen": { "height": 878636 } } ], "vout": [ { "amount": 752859973, "target": { "key": "701bc6e8e62d10d3d9c77f31d8bf63a84e13bf6cb96c17cbf46f90b708f96a11" } } ], "extra": [ 1, 119, 42, 28, 169, 254, 117, 178, 5, 37, 226, 69, 168, 111, 254, 187, 68, 49, 215, 208, 172, 2, 104, 139, 81, 139, 153, 206, 133, 48, 86, 12, 231, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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