Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a613b4dee45e24c2cfe3e5915ed947afb0f8ea8721d73e154b96b18f1369026

Tx prefix hash: 66c576702dbdb332c7478cb99458e4cc5b552cece093b8f2a1382b28626ec469
Tx public key: 5742858de4c9ef37d834610cc3582b4ab870b4ebba4cfdad15bda4f8f4e9e3a9
Timestamp: 1752179811 Timestamp [UCT]: 2025-07-10 20:36:51 Age [y:d:h:m:s]: 00:044:23:09:13
Block: 1322844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30787 RingCT/type: yes/0
Extra: 015742858de4c9ef37d834610cc3582b4ab870b4ebba4cfdad15bda4f8f4e9e3a9021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0fc37b36f821f6c7f01d82822e2722e4ac35d4dbbc1095dd0c7b4ede1dd7f6b 0.600000000000 1810577 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": 1322854, "vin": [ { "gen": { "height": 1322844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0fc37b36f821f6c7f01d82822e2722e4ac35d4dbbc1095dd0c7b4ede1dd7f6b" } } ], "extra": [ 1, 87, 66, 133, 141, 228, 201, 239, 55, 216, 52, 97, 12, 195, 88, 43, 74, 184, 112, 180, 235, 186, 76, 253, 173, 21, 189, 164, 248, 244, 233, 227, 169, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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