Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1b1d7b46be6d0c3f44963fb79288b64bad27a4ce03fb0d20d2f07c1bedbefbc

Tx prefix hash: ed16369bd3f82e786be3b08c0c2997cef57b5baccb4967de2bbe1e0e21d1383a
Tx public key: b30039655b1128fbe69ac0632e25d1dcaac62e3b2d250bcfd8f751013bb14b8b
Timestamp: 1737252412 Timestamp [UCT]: 2025-01-19 02:06:52 Age [y:d:h:m:s]: 00:150:22:07:59
Block: 1200406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107588 RingCT/type: yes/0
Extra: 01b30039655b1128fbe69ac0632e25d1dcaac62e3b2d250bcfd8f751013bb14b8b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f24b0f8d1c649dd5d981788ff1322d6e5f158b1b3d84c13d02ad897a8517e121 0.600000000000 1687049 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": 1200416, "vin": [ { "gen": { "height": 1200406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f24b0f8d1c649dd5d981788ff1322d6e5f158b1b3d84c13d02ad897a8517e121" } } ], "extra": [ 1, 179, 0, 57, 101, 91, 17, 40, 251, 230, 154, 192, 99, 46, 37, 209, 220, 170, 198, 46, 59, 45, 37, 11, 207, 216, 247, 81, 1, 59, 177, 75, 139, 2, 17, 0, 0, 0, 2, 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