Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50a2a0c203ecf6e10f804da5360e811ddfb89398cc4b07e6b4bd2b33013128c8

Tx prefix hash: aec7bc31fafd001724c3894d682bcae848e423f4c1dd7396dc6a23c8b72ad19e
Tx public key: 75080c0bb787ed539e88bb52ca0cb2151f1ab54a438ec91d1481c812bf30aadf
Timestamp: 1759615081 Timestamp [UTC]: 2025-10-04 21:58:01 Age [y:d:h:m:s]: 01:044:08:21:54
Block: 1382862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298071 RingCT/type: yes/0
Extra: 0175080c0bb787ed539e88bb52ca0cb2151f1ab54a438ec91d1481c812bf30aadf021100000003a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9b8c7525d25aa37f0e0b1ccd22282dd79c3ae2e58b340454dfa2c3286b6645bc 0.000600000000 1871007 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": 1382872, "vin": [ { "gen": { "height": 1382862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b8c7525d25aa37f0e0b1ccd22282dd79c3ae2e58b340454dfa2c3286b6645bc" } } ], "extra": [ 1, 117, 8, 12, 11, 183, 135, 237, 83, 158, 136, 187, 82, 202, 12, 178, 21, 31, 26, 181, 74, 67, 142, 201, 29, 20, 129, 200, 18, 191, 48, 170, 223, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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: