Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ac298e0f05593e7d4c6efb4da1ea424b37dc7b00bd2506ab229623169efb7c0

Tx prefix hash: 8f81f1440aeecce472b94a70357e93dc5928f5537a4d1d16cd58644e69e1cdf6
Tx public key: efeb5d441e50d0340231a9a32b9704f2531f25b129902b9e67f923653d0f24ad
Timestamp: 1737787458 Timestamp [UCT]: 2025-01-25 06:44:18 Age [y:d:h:m:s]: 00:143:09:53:57
Block: 1204830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102241 RingCT/type: yes/0
Extra: 01efeb5d441e50d0340231a9a32b9704f2531f25b129902b9e67f923653d0f24ad021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8af7c62f63d506029e62beb2cdeee30af425cc61f2cdccf6171db09abfc5771e 0.600000000000 1691523 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": 1204840, "vin": [ { "gen": { "height": 1204830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8af7c62f63d506029e62beb2cdeee30af425cc61f2cdccf6171db09abfc5771e" } } ], "extra": [ 1, 239, 235, 93, 68, 30, 80, 208, 52, 2, 49, 169, 163, 43, 151, 4, 242, 83, 31, 37, 177, 41, 144, 43, 158, 103, 249, 35, 101, 61, 15, 36, 173, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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