Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fcf2b70726b4389c3fd454d44a500a27daa49f77c48b57c45132eadbefae7d3

Tx prefix hash: 5b86afb00d8e0074350d07596c06e3df36d314b0f9a7994000b3d4211a1e9168
Tx public key: 2884cd3c78f8ed187ab90f73e3e2196baca72bccdc08b1e427721ae5c25454c9
Timestamp: 1773681043 Timestamp [UTC]: 2026-03-16 17:10:43 Age [y:d:h:m:s]: 00:063:14:53:05
Block: 1499225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38891 RingCT/type: yes/0
Extra: 012884cd3c78f8ed187ab90f73e3e2196baca72bccdc08b1e427721ae5c25454c9021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8bc453e6ed1e552ca460c85791dbadcc3c2b08651e4364ff047643bc6098ff72 0.000600000000 1988879 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": 1499235, "vin": [ { "gen": { "height": 1499225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bc453e6ed1e552ca460c85791dbadcc3c2b08651e4364ff047643bc6098ff72" } } ], "extra": [ 1, 40, 132, 205, 60, 120, 248, 237, 24, 122, 185, 15, 115, 227, 226, 25, 107, 172, 167, 43, 204, 220, 8, 177, 228, 39, 114, 26, 229, 194, 84, 84, 201, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: