Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6a65f652fc17dab8ac2b2fd3136328fdf16225454bbe566c5bb88f36459ec5

Tx prefix hash: 17701e266a42b5a0e1cfc98efbf1284af7a59851805d4d23526ca43b60f6c10f
Tx public key: 6d22b3ac3d78734effd20ad213bf90cbb588936dbb85e7302dbfd49718fd8e9f
Timestamp: 1741245796 Timestamp [UTC]: 2025-03-06 07:23:16 Age [y:d:h:m:s]: 01:260:19:03:19
Block: 1233231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450263 RingCT/type: yes/0
Extra: 016d22b3ac3d78734effd20ad213bf90cbb588936dbb85e7302dbfd49718fd8e9f021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d74540297e0a3d91a9bccb325b5beb7ef1cb64305fa95445cfe7ef644a8077cb 0.000600000000 1720150 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": 1233241, "vin": [ { "gen": { "height": 1233231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d74540297e0a3d91a9bccb325b5beb7ef1cb64305fa95445cfe7ef644a8077cb" } } ], "extra": [ 1, 109, 34, 179, 172, 61, 120, 115, 78, 255, 210, 10, 210, 19, 191, 144, 203, 181, 136, 147, 109, 187, 133, 231, 48, 45, 191, 212, 151, 24, 253, 142, 159, 2, 17, 0, 0, 0, 6, 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: