Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a0eef2642f26b9ce8babf0e0f9e94fa70e0e693f4bd8b4ea8aaccb525806067

Tx prefix hash: 91ab9e1ab3339ec1e87441efd52915ec15e7a2e5e3faf4c51b44142131dd0528
Tx public key: 5b7beaeec64a9b47675ca0bcff250c003b287e9b6d6e3b4e2d8532dec079bb27
Timestamp: 1740760701 Timestamp [UTC]: 2025-02-28 16:38:21 Age [y:d:h:m:s]: 01:264:09:54:02
Block: 1229205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453131 RingCT/type: yes/0
Extra: 015b7beaeec64a9b47675ca0bcff250c003b287e9b6d6e3b4e2d8532dec079bb27021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ebb89a76d2a8ab3045fbe37a38b55d53de8b9c29d8abb05211553f293be9bee9 0.000600000000 1716090 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": 1229215, "vin": [ { "gen": { "height": 1229205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebb89a76d2a8ab3045fbe37a38b55d53de8b9c29d8abb05211553f293be9bee9" } } ], "extra": [ 1, 91, 123, 234, 238, 198, 74, 155, 71, 103, 92, 160, 188, 255, 37, 12, 0, 59, 40, 126, 155, 109, 110, 59, 78, 45, 133, 50, 222, 192, 121, 187, 39, 2, 17, 0, 0, 0, 5, 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: