Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652c696aa5644ad25bda1b69725b1e6866d3d503be5dd053c088adafe1e4f1dd

Tx prefix hash: fd03620148eb233951d21cb413493cba953678ecd3ab07b14ff4a227ff6f4c6d
Tx public key: 2d09fbdbf7283db824734c5360ad711b3c6323d5cf1b9cb08b568322d0454993
Timestamp: 1765474982 Timestamp [UCT]: 2025-12-11 17:43:02 Age [y:d:h:m:s]: 00:026:21:19:55
Block: 1431431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19263 RingCT/type: yes/0
Extra: 012d09fbdbf7283db824734c5360ad711b3c6323d5cf1b9cb08b568322d045499302110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8359ffdf4fb2ef16607f0ae7eda0d9612b0da55cf83c44fc9d8ecc36e41a46a9 0.600000000000 1920202 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": 1431441, "vin": [ { "gen": { "height": 1431431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8359ffdf4fb2ef16607f0ae7eda0d9612b0da55cf83c44fc9d8ecc36e41a46a9" } } ], "extra": [ 1, 45, 9, 251, 219, 247, 40, 61, 184, 36, 115, 76, 83, 96, 173, 113, 27, 60, 99, 35, 213, 207, 27, 156, 176, 139, 86, 131, 34, 208, 69, 73, 147, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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