Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 131a79e21a3ff234156cc69f07f50af7726fed5b9be6e92e651bf0d0bf95b3d3

Tx prefix hash: 3ab6218502d9ef7dc517c837b69cd7db41d1c29e204e9f6201cb8071a67b7b02
Tx public key: 54636e37bf6374fa673976f8c9f4b3ac8c939db6f4cf893134584a362c47e44d
Timestamp: 1625465014 Timestamp [UTC]: 2021-07-05 06:03:34 Age [y:d:h:m:s]: 05:141:04:58:49
Block: 288482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1395012 RingCT/type: yes/0
Extra: 0154636e37bf6374fa673976f8c9f4b3ac8c939db6f4cf893134584a362c47e44d021100000010b8178fc1000000000000000000

1 output(s) for total of 0.067942243992 xmr

stealth address amount amount idx tag
00: 9e34ba0bd7f6aab3797bb3b32549f9ea7c096d39ee0a891f4baea2cb5997fe4d 0.067942243992 604395 of 0 -

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": 288492, "vin": [ { "gen": { "height": 288482 } } ], "vout": [ { "amount": 67942243992, "target": { "key": "9e34ba0bd7f6aab3797bb3b32549f9ea7c096d39ee0a891f4baea2cb5997fe4d" } } ], "extra": [ 1, 84, 99, 110, 55, 191, 99, 116, 250, 103, 57, 118, 248, 201, 244, 179, 172, 140, 147, 157, 182, 244, 207, 137, 49, 52, 88, 74, 54, 44, 71, 228, 77, 2, 17, 0, 0, 0, 16, 184, 23, 143, 193, 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: