Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 164d6eebb5b747cbe76bb6a87a1ed6df34aa33e23ce711da9003df9d10316f3a

Tx prefix hash: 3f9035df85b5b2901a9c4c360aa6f28c8b6a80e52b596e264aac35070ded5708
Tx public key: d370a7d514660ac6c4d88b9dc8dcdab2631e41835f6c99396d4d68c4e63f2922
Timestamp: 1753293593 Timestamp [UTC]: 2025-07-23 17:59:53 Age [y:d:h:m:s]: 00:346:20:48:13
Block: 1331806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243492 RingCT/type: yes/0
Extra: 01d370a7d514660ac6c4d88b9dc8dcdab2631e41835f6c99396d4d68c4e63f2922021100000001e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 27908c6e4ccb260b932d59864f8fb8ef15638436885b3b17db5df6232660e358 0.000600000000 1819603 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": 1331816, "vin": [ { "gen": { "height": 1331806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27908c6e4ccb260b932d59864f8fb8ef15638436885b3b17db5df6232660e358" } } ], "extra": [ 1, 211, 112, 167, 213, 20, 102, 10, 198, 196, 216, 139, 157, 200, 220, 218, 178, 99, 30, 65, 131, 95, 108, 153, 57, 109, 77, 104, 196, 230, 63, 41, 34, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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: