Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f24aeaa1cf303d666470ad3d33c775001e3fbefd766901613e47fcd7788735eb

Tx prefix hash: e49d4a6e5c7578145ecea9ba8f62f4caeab43d3a395a67b9b4ad18be90e464c4
Tx public key: 0f45a7425db297c12d414af7ef0cc35ebd70d796aed7850c8c638bba0da25a3b
Timestamp: 1762977539 Timestamp [UCT]: 2025-11-12 19:58:59 Age [y:d:h:m:s]: 00:041:08:44:24
Block: 1410735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29615 RingCT/type: yes/0
Extra: 010f45a7425db297c12d414af7ef0cc35ebd70d796aed7850c8c638bba0da25a3b0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fed80542d583b35f658d8ca12c423af6cb43a02a8230035b4f0e33afd43e4c6 0.600000000000 1899188 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": 1410745, "vin": [ { "gen": { "height": 1410735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fed80542d583b35f658d8ca12c423af6cb43a02a8230035b4f0e33afd43e4c6" } } ], "extra": [ 1, 15, 69, 167, 66, 93, 178, 151, 193, 45, 65, 74, 247, 239, 12, 195, 94, 189, 112, 215, 150, 174, 215, 133, 12, 140, 99, 139, 186, 13, 162, 90, 59, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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