Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6774035552447cde2c06e577ea8388e96e9f558b9d246bd17ebcf84d2829ac86

Tx prefix hash: 6c09a15aec1fc3633cade3127c6123486f7d7cdfbf0c063bdd83dbd4294e78ef
Tx public key: 01e77011ba8b135b3b8bc40c512d9ebf0a40fcbc565a533fa2df2f459206e92b
Timestamp: 1751166100 Timestamp [UCT]: 2025-06-29 03:01:40 Age [y:d:h:m:s]: 00:186:14:12:28
Block: 1314944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131508 RingCT/type: yes/0
Extra: 0101e77011ba8b135b3b8bc40c512d9ebf0a40fcbc565a533fa2df2f459206e92b021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 778828a10cebe9c5079d38d1b4e5f7237016b19b804a957f616b7074ac59f23e 0.600000000000 1802597 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": 1314954, "vin": [ { "gen": { "height": 1314944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "778828a10cebe9c5079d38d1b4e5f7237016b19b804a957f616b7074ac59f23e" } } ], "extra": [ 1, 1, 231, 112, 17, 186, 139, 19, 91, 59, 139, 196, 12, 81, 45, 158, 191, 10, 64, 252, 188, 86, 90, 83, 63, 162, 223, 47, 69, 146, 6, 233, 43, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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