Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4e06fb3416f5ba0bd2f06c61060c11e4e71ff46fb8bd9b4e02837771dc8a6c8

Tx prefix hash: 003e8919804e032f6a4ad5357a1ed2f2f329a5b8735b9bf9dc4604514bbd2b6c
Tx public key: f26df40de5ff1f52643938653825d68273b222e980bdff2650f13642ccc1d8fc
Timestamp: 1774227501 Timestamp [UTC]: 2026-03-23 00:58:21 Age [y:d:h:m:s]: 00:238:08:55:09
Block: 1503724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175838 RingCT/type: yes/0
Extra: 01f26df40de5ff1f52643938653825d68273b222e980bdff2650f13642ccc1d8fc021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b2f79996770b09f9bbdb3ea5751c290500857a6782bc29fce698b6099eb4006 0.000600000000 1993436 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": 1503734, "vin": [ { "gen": { "height": 1503724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b2f79996770b09f9bbdb3ea5751c290500857a6782bc29fce698b6099eb4006" } } ], "extra": [ 1, 242, 109, 244, 13, 229, 255, 31, 82, 100, 57, 56, 101, 56, 37, 214, 130, 115, 178, 34, 233, 128, 189, 255, 38, 80, 241, 54, 66, 204, 193, 216, 252, 2, 17, 0, 0, 0, 3, 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: