Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02d91a6b0b16eb52e1ddc701f0d3fdc40b18e6fe179ff9a1756cbebba44cc9eb

Tx prefix hash: 7355243118efd1b777ab5c52d8645af39f1ec702ae452e2b2d6d46b56d7d06d2
Tx public key: f38791292a864800d7509b213e09bf7479d57b9951e5efa758c19efef9870bd1
Timestamp: 1769752321 Timestamp [UTC]: 2026-01-30 05:52:01 Age [y:d:h:m:s]: 00:207:00:43:11
Block: 1466707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153798 RingCT/type: yes/0
Extra: 01f38791292a864800d7509b213e09bf7479d57b9951e5efa758c19efef9870bd102110000000149d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 697f4948a441bf7babe7000a0a55a4ac0c80b2cb557388537dbd972adc193fca 0.000600000000 1955943 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": 1466717, "vin": [ { "gen": { "height": 1466707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "697f4948a441bf7babe7000a0a55a4ac0c80b2cb557388537dbd972adc193fca" } } ], "extra": [ 1, 243, 135, 145, 41, 42, 134, 72, 0, 215, 80, 155, 33, 62, 9, 191, 116, 121, 213, 123, 153, 81, 229, 239, 167, 88, 193, 158, 254, 249, 135, 11, 209, 2, 17, 0, 0, 0, 1, 73, 215, 62, 152, 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: