Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a2fcb44eab5416000890e59db675aa51b881649fb8d871d56e3bc64f9acffff

Tx prefix hash: a56ad0f2696f169f77e05ac77499640c95ab17d5b6f763fa129545b9d649ec3b
Tx public key: 7579d8b59569ed270395d7451586f4a69e58483b57753ea7a5389c9d4c367563
Timestamp: 1742031065 Timestamp [UTC]: 2025-03-15 09:31:05 Age [y:d:h:m:s]: 01:064:23:25:59
Block: 1239751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298394 RingCT/type: yes/0
Extra: 017579d8b59569ed270395d7451586f4a69e58483b57753ea7a5389c9d4c367563021100000007007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 135bd4eba88d7850fd3db7cdade9af3a336d1df9c7588fb7ae45bb955b477c4d 0.000600000000 1726716 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": 1239761, "vin": [ { "gen": { "height": 1239751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "135bd4eba88d7850fd3db7cdade9af3a336d1df9c7588fb7ae45bb955b477c4d" } } ], "extra": [ 1, 117, 121, 216, 181, 149, 105, 237, 39, 3, 149, 215, 69, 21, 134, 244, 166, 158, 88, 72, 59, 87, 117, 62, 167, 165, 56, 156, 157, 76, 54, 117, 99, 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): devel-2026-02-02-6303d2a (1.2) | monero version: