Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d723570df28c8df82b239bf4bbc9885728a37872ea7681b8a8bf3f78977a7167

Tx prefix hash: bd18934b8081c65fb6ec04c1bdeff5d5be19bfaf2faa87565f9d5070c1cc9ed8
Tx public key: 62e8222d9cf8d1cbcf4b843a3b22553f71e2ac478923c54fb0e67a42cc8d5bda
Timestamp: 1741237216 Timestamp [UTC]: 2025-03-06 05:00:16 Age [y:d:h:m:s]: 01:260:14:35:09
Block: 1233156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450338 RingCT/type: yes/0
Extra: 0162e8222d9cf8d1cbcf4b843a3b22553f71e2ac478923c54fb0e67a42cc8d5bda021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8ede69c022f9aa83dfb9285f1594dbb8fa5ad4f4908e665e9c543a6763129c0f 0.000600000000 1720075 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": 1233166, "vin": [ { "gen": { "height": 1233156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ede69c022f9aa83dfb9285f1594dbb8fa5ad4f4908e665e9c543a6763129c0f" } } ], "extra": [ 1, 98, 232, 34, 45, 156, 248, 209, 203, 207, 75, 132, 58, 59, 34, 85, 63, 113, 226, 172, 71, 137, 35, 197, 79, 176, 230, 122, 66, 204, 141, 91, 218, 2, 17, 0, 0, 0, 4, 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: