Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b211765c3e263d85b1ff4c65f7d647caef3bcdb4de0f58f70d1fc387460075f

Tx prefix hash: 682a1d6d0a86a1c9280831e99fbbdf32c677c8ff3614c57782d04afc08fb36d7
Tx public key: 543af33bd9e5c505698a98f448b5f08d5fe035e9955d643930799e96b7f22728
Timestamp: 1742002959 Timestamp [UTC]: 2025-03-15 01:42:39 Age [y:d:h:m:s]: 01:243:04:51:32
Block: 1239519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437690 RingCT/type: yes/0
Extra: 01543af33bd9e5c505698a98f448b5f08d5fe035e9955d643930799e96b7f22728021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0611bfa0371c9132d949d5fe9cd17ad35de224f569ff00b2ba789824f3252fc5 0.000600000000 1726484 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": 1239529, "vin": [ { "gen": { "height": 1239519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0611bfa0371c9132d949d5fe9cd17ad35de224f569ff00b2ba789824f3252fc5" } } ], "extra": [ 1, 84, 58, 243, 59, 217, 229, 197, 5, 105, 138, 152, 244, 72, 181, 240, 141, 95, 224, 53, 233, 149, 93, 100, 57, 48, 121, 158, 150, 183, 242, 39, 40, 2, 17, 0, 0, 0, 2, 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: