Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b33aed84086c1849762b8adcf00a94feb1b918c9373d8757964d22ef9b42fc36

Tx prefix hash: 91a79129f4404a7bd7512ae655093a727fcb4600d6c52f9fb42eb45e2457a2fa
Tx public key: 6e6e6a864a870de6f8f3125f7e2daa6d0f6ce90dbde248ce8edbfb69320a4031
Timestamp: 1723753204 Timestamp [UTC]: 2024-08-15 20:20:04 Age [y:d:h:m:s]: 02:096:03:51:19
Block: 1088675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593580 RingCT/type: yes/0
Extra: 016e6e6a864a870de6f8f3125f7e2daa6d0f6ce90dbde248ce8edbfb69320a4031021100000005e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 091bd0160b1618918e43bf9c62737bc717439bfc790e9779f160a784e6978912 0.000600000000 1563292 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 dinastycoin-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": 1088685, "vin": [ { "gen": { "height": 1088675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "091bd0160b1618918e43bf9c62737bc717439bfc790e9779f160a784e6978912" } } ], "extra": [ 1, 110, 110, 106, 134, 74, 135, 13, 230, 248, 243, 18, 95, 126, 45, 170, 109, 15, 108, 233, 13, 189, 226, 72, 206, 142, 219, 251, 105, 50, 10, 64, 49, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: