Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b51b0f31d650c3f9fb2a5c0a25037cf2ec33442640c744b5345db6061e8395

Tx prefix hash: 73b04d0a47109176ca825bef010ad2146dcd8c2be90c970497b1a5cd383e0155
Tx public key: 4fa96c76a9b32612f809973ac1a2eff32dd093a26a28e58aa5f556d8935b4aab
Timestamp: 1712802531 Timestamp [UCT]: 2024-04-11 02:28:51 Age [y:d:h:m:s]: 01:268:02:03:02
Block: 997858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450372 RingCT/type: yes/0
Extra: 014fa96c76a9b32612f809973ac1a2eff32dd093a26a28e58aa5f556d8935b4aab0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 828ae0798b59cfad1f41e441cc9e0f6f13d1f8a7bbf67abc7a36aab219f679e7 0.600000000000 1458292 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": 997868, "vin": [ { "gen": { "height": 997858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "828ae0798b59cfad1f41e441cc9e0f6f13d1f8a7bbf67abc7a36aab219f679e7" } } ], "extra": [ 1, 79, 169, 108, 118, 169, 179, 38, 18, 248, 9, 151, 58, 193, 162, 239, 243, 45, 208, 147, 162, 106, 40, 229, 138, 165, 245, 86, 216, 147, 91, 74, 171, 2, 17, 0, 0, 0, 5, 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