Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 973371a42d8dbcba82121db938b862f0c415b9cda0c3cc2e4a9611d4d4b6358d

Tx prefix hash: 435331fbc4a41f7b00d05538774e0349b272f20d678c08f58d52795b7515f585
Tx public key: 97a1d8f9ac5e2d1f4676452df81c9af242cc6314ef99e8136bfd97e7649615a6
Timestamp: 1747835676 Timestamp [UTC]: 2025-05-21 13:54:36 Age [y:d:h:m:s]: 01:179:18:39:58
Block: 1287794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392470 RingCT/type: yes/0
Extra: 0197a1d8f9ac5e2d1f4676452df81c9af242cc6314ef99e8136bfd97e7649615a60211000000061f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: eb98ff6033755c61490dc1d2291d5535dfcd0e82ea5b262abd8a3ad250edb378 0.000600000000 1775261 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": 1287804, "vin": [ { "gen": { "height": 1287794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb98ff6033755c61490dc1d2291d5535dfcd0e82ea5b262abd8a3ad250edb378" } } ], "extra": [ 1, 151, 161, 216, 249, 172, 94, 45, 31, 70, 118, 69, 45, 248, 28, 154, 242, 66, 204, 99, 20, 239, 153, 232, 19, 107, 253, 151, 231, 100, 150, 21, 166, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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: