Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b03deba06502a4277abdd30bad02da21c089b74db742f30ff42e318c2c538d7

Tx prefix hash: 53948648efb2a65a4cf39aefa2e0e35526d19380c530ded87d0688c2dabef7c5
Tx public key: 1b9a6e218fd555c67c66a9f42836a517fe5967f8d0b0f92715726cecb79cdc84
Timestamp: 1775244517 Timestamp [UTC]: 2026-04-03 19:28:37 Age [y:d:h:m:s]: 00:228:11:25:21
Block: 1512157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168798 RingCT/type: yes/0
Extra: 011b9a6e218fd555c67c66a9f42836a517fe5967f8d0b0f92715726cecb79cdc84021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9234bcd124acb9bdd8200793ebffc07e05de886413f62e6e1bb0c1d070b08b42 0.000600000000 2001955 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": 1512167, "vin": [ { "gen": { "height": 1512157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9234bcd124acb9bdd8200793ebffc07e05de886413f62e6e1bb0c1d070b08b42" } } ], "extra": [ 1, 27, 154, 110, 33, 143, 213, 85, 198, 124, 102, 169, 244, 40, 54, 165, 23, 254, 89, 103, 248, 208, 176, 249, 39, 21, 114, 108, 236, 183, 156, 220, 132, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: