Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9e8adfe8b917a1e6c2a413b295c9e3c718393ec8b7ca020cba88a599a002cc2

Tx prefix hash: 863840df03fac16b5d643d016523c341c534349180780f85a7229d7c2bf16223
Tx public key: 39479d01671d80291f1c54171af97d5e83e073f8dbbfe247b4d8e2db2787cf0a
Timestamp: 1763025844 Timestamp [UCT]: 2025-11-13 09:24:04 Age [y:d:h:m:s]: 00:014:21:28:02
Block: 1411138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10662 RingCT/type: yes/0
Extra: 0139479d01671d80291f1c54171af97d5e83e073f8dbbfe247b4d8e2db2787cf0a0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 538d26c2644db9c87a203bf02e59200fb329cbade3ce895d047c391f34f891ac 0.600000000000 1899595 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": 1411148, "vin": [ { "gen": { "height": 1411138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "538d26c2644db9c87a203bf02e59200fb329cbade3ce895d047c391f34f891ac" } } ], "extra": [ 1, 57, 71, 157, 1, 103, 29, 128, 41, 31, 28, 84, 23, 26, 249, 125, 94, 131, 224, 115, 248, 219, 191, 226, 71, 180, 216, 226, 219, 39, 135, 207, 10, 2, 17, 0, 0, 0, 4, 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