Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f70a690abc23e99de05d1af442de4de8ad560df9ec44140e667a7dda7628acd2

Tx prefix hash: 947d3ad10ec67ccb14c16566428fe2b6f22c79d9723c15c8858abdb491058e04
Tx public key: 38d76809b2b041c7e975148a423fbbfeaec883e4f7093c9cfbbe7d959693e843
Timestamp: 1738614026 Timestamp [UTC]: 2025-02-03 20:20:26 Age [y:d:h:m:s]: 01:290:17:44:18
Block: 1211434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472021 RingCT/type: yes/0
Extra: 0138d76809b2b041c7e975148a423fbbfeaec883e4f7093c9cfbbe7d959693e843021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6fd32b5221d2f94ca31fb9c215f226f11174e5560542ac69413dd8cffa975df6 0.000600000000 1698195 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": 1211444, "vin": [ { "gen": { "height": 1211434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fd32b5221d2f94ca31fb9c215f226f11174e5560542ac69413dd8cffa975df6" } } ], "extra": [ 1, 56, 215, 104, 9, 178, 176, 65, 199, 233, 117, 20, 138, 66, 63, 187, 254, 174, 200, 131, 228, 247, 9, 60, 156, 251, 190, 125, 149, 150, 147, 232, 67, 2, 17, 0, 0, 0, 1, 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: