Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c580abae5911f00adc30a5990be6703f3ef068ffe9884f7032af746994f68310

Tx prefix hash: b018e3550e013fff7fe825444a1bf9719f05e5a98c2c79daf15fa585a6f583e5
Tx public key: d533ae8a699178211551a88ae02b44b36ee4be063ae7cc9157f1f0ed93304d0c
Timestamp: 1756065520 Timestamp [UCT]: 2025-08-24 19:58:40 Age [y:d:h:m:s]: 00:093:18:26:51
Block: 1353639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66953 RingCT/type: yes/0
Extra: 01d533ae8a699178211551a88ae02b44b36ee4be063ae7cc9157f1f0ed93304d0c0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeda1bd92b2ac50b1d07752b3aec98862a292ad5fd31991e16290b01914dcbde 0.600000000000 1841616 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": 1353649, "vin": [ { "gen": { "height": 1353639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeda1bd92b2ac50b1d07752b3aec98862a292ad5fd31991e16290b01914dcbde" } } ], "extra": [ 1, 213, 51, 174, 138, 105, 145, 120, 33, 21, 81, 168, 138, 224, 43, 68, 179, 110, 228, 190, 6, 58, 231, 204, 145, 87, 241, 240, 237, 147, 48, 77, 12, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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