Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a0c907e2607438adaa2045d074f2c6a9c401f0cef26fe05452d13fcd15af803

Tx prefix hash: 865927b0271a96c144bec6a66648b18cbef72ce4b20f3cec7f9e3ac02834cbe2
Tx public key: 0a9016ed5e84e2576dfa9125ddc941efccc98d639983b7a9b231cd2326bfd2fb
Timestamp: 1714436379 Timestamp [UCT]: 2024-04-30 00:19:39 Age [y:d:h:m:s]: 00:272:18:49:08
Block: 1011426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194999 RingCT/type: yes/0
Extra: 010a9016ed5e84e2576dfa9125ddc941efccc98d639983b7a9b231cd2326bfd2fb0211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b14c3ac48429166f152488553fb01290b54c9e07d9f9f52b58f42cb97393378b 0.600000000000 1473652 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": 1011436, "vin": [ { "gen": { "height": 1011426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b14c3ac48429166f152488553fb01290b54c9e07d9f9f52b58f42cb97393378b" } } ], "extra": [ 1, 10, 144, 22, 237, 94, 132, 226, 87, 109, 250, 145, 37, 221, 201, 65, 239, 204, 201, 141, 99, 153, 131, 183, 169, 178, 49, 205, 35, 38, 191, 210, 251, 2, 17, 0, 0, 0, 16, 122, 156, 244, 199, 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