Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9950addd446d4b1aacdd6f3b78bf19d3d0b36850eed8156f3b7994eba0c9d37d

Tx prefix hash: d3891db2b79efb0d9b53dc4d7bb3a1e6c0307feda1136259be52ab07108d40d8
Tx public key: b826acecde7e7d368aaa56d160f90ad5efc691d8afd905b78d71f859c32c91aa
Timestamp: 1765723729 Timestamp [UCT]: 2025-12-14 14:48:49 Age [y:d:h:m:s]: 00:008:19:50:18
Block: 1433494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6304 RingCT/type: yes/0
Extra: 01b826acecde7e7d368aaa56d160f90ad5efc691d8afd905b78d71f859c32c91aa021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f1269defd5fedfc443b4efa442230e44b4d8e0afb86781647b1a7ef0fca96e5 0.600000000000 1922273 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": 1433504, "vin": [ { "gen": { "height": 1433494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f1269defd5fedfc443b4efa442230e44b4d8e0afb86781647b1a7ef0fca96e5" } } ], "extra": [ 1, 184, 38, 172, 236, 222, 126, 125, 54, 138, 170, 86, 209, 96, 249, 10, 213, 239, 198, 145, 216, 175, 217, 5, 183, 141, 113, 248, 89, 195, 44, 145, 170, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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