Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa1a3d9c311b93057cc42b055a8a4f04d11ed765e983d02c84b762bc71aed39d

Tx prefix hash: 1e5c13e114eea5c7c330e11965b8bfc181aa047c4c3a0a177dc68873fec05da6
Tx public key: 8584752dbfbc7c55b234f231c50d840eb836386339e72796a0dacea8dcfe05aa
Timestamp: 1773777275 Timestamp [UTC]: 2026-03-17 19:54:35 Age [y:d:h:m:s]: 00:241:21:48:27
Block: 1499987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178313 RingCT/type: yes/0
Extra: 018584752dbfbc7c55b234f231c50d840eb836386339e72796a0dacea8dcfe05aa021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4c58c6dc4ca8105fbb87b9ad9e2dfbc84f34e6a3fa4056e09553815428ea0496 0.000600000000 1989651 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": 1499997, "vin": [ { "gen": { "height": 1499987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c58c6dc4ca8105fbb87b9ad9e2dfbc84f34e6a3fa4056e09553815428ea0496" } } ], "extra": [ 1, 133, 132, 117, 45, 191, 188, 124, 85, 178, 52, 242, 49, 197, 13, 132, 14, 184, 54, 56, 99, 57, 231, 39, 150, 160, 218, 206, 168, 220, 254, 5, 170, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: