Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fff00dab21ac94424fe2a3665661e6e5f2123d8836c0a1a24651669bc3f4a0ef

Tx prefix hash: e26247463eba1d4b8acc8cf6406f0f9f48fa8f1df3a914e89c0f9c1a2011b789
Tx public key: c75b7028ed64ee8d27cd2882ea9dbd2819969ea806a3e9d64c17acf685d90728
Timestamp: 1757682363 Timestamp [UCT]: 2025-09-12 13:06:03 Age [y:d:h:m:s]: 00:102:10:01:18
Block: 1366850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73328 RingCT/type: yes/0
Extra: 01c75b7028ed64ee8d27cd2882ea9dbd2819969ea806a3e9d64c17acf685d90728021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 314944c71f092eb0285027b0184760e54f463a47fdc853e688c983fe98977f99 0.600000000000 1854889 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": 1366860, "vin": [ { "gen": { "height": 1366850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "314944c71f092eb0285027b0184760e54f463a47fdc853e688c983fe98977f99" } } ], "extra": [ 1, 199, 91, 112, 40, 237, 100, 238, 141, 39, 205, 40, 130, 234, 157, 189, 40, 25, 150, 158, 168, 6, 163, 233, 214, 76, 23, 172, 246, 133, 217, 7, 40, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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