Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a7049b2d0f945105ebfe0229cc03a24c3a5f5ef66cb1d40b2f6132986631a98

Tx prefix hash: dc24fb8f42510daf7d380de9ffeb6105a33d7aa7e36e55fe0725c171ed513d7c
Tx public key: cd4bf0f6d72aed3110f82ed6f8d278420adc94619db863745fef4245a80df85e
Timestamp: 1749199722 Timestamp [UCT]: 2025-06-06 08:48:42 Age [y:d:h:m:s]: 00:167:19:13:43
Block: 1299088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117602 RingCT/type: yes/0
Extra: 01cd4bf0f6d72aed3110f82ed6f8d278420adc94619db863745fef4245a80df85e02110000000abf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b786c5c4621cdfaa0d930127227b516e8682670bf6a3dfdb8ab751b88487e48f 0.600000000000 1786623 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": 1299098, "vin": [ { "gen": { "height": 1299088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b786c5c4621cdfaa0d930127227b516e8682670bf6a3dfdb8ab751b88487e48f" } } ], "extra": [ 1, 205, 75, 240, 246, 215, 42, 237, 49, 16, 248, 46, 214, 248, 210, 120, 66, 10, 220, 148, 97, 157, 184, 99, 116, 95, 239, 66, 69, 168, 13, 248, 94, 2, 17, 0, 0, 0, 10, 191, 81, 178, 162, 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