Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8e2436d71e144e923a3ce3af70f3483343537750f5c78caadd2bdd598add4c7

Tx prefix hash: 3d72bc9cd2e3497570cf0cdd6a2bd6da8792126118476b51c080f7fc5f3036d0
Tx public key: 6a10a299622fa7d058a388bfa878ba271d7c75d10ac26ee38fc24b1bf5f4b80e
Timestamp: 1756109089 Timestamp [UCT]: 2025-08-25 08:04:49 Age [y:d:h:m:s]: 00:159:09:46:32
Block: 1353997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113773 RingCT/type: yes/0
Extra: 016a10a299622fa7d058a388bfa878ba271d7c75d10ac26ee38fc24b1bf5f4b80e021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4be8f5a310c2d793c9e078c0876b72bb50d40bf372d05db4885c40d4460c4a23 0.600000000000 1841978 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": 1354007, "vin": [ { "gen": { "height": 1353997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4be8f5a310c2d793c9e078c0876b72bb50d40bf372d05db4885c40d4460c4a23" } } ], "extra": [ 1, 106, 16, 162, 153, 98, 47, 167, 208, 88, 163, 136, 191, 168, 120, 186, 39, 29, 124, 117, 209, 10, 194, 110, 227, 143, 194, 75, 27, 245, 244, 184, 14, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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