Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb24637174cca0d07690da80e8a852fc994337b73cb4d9e937a901a55e0476f5

Tx prefix hash: afcfad832f3d5280a59106c3bd7b43fd4513bda63d7ff1fe9442e76f50a0bb19
Tx public key: 0c6370975225d1e57934cafc6f611e7b112ef23e55a3e09a9004a16da83457bf
Timestamp: 1738083581 Timestamp [UTC]: 2025-01-28 16:59:41 Age [y:d:h:m:s]: 01:104:18:11:09
Block: 1207056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325749 RingCT/type: yes/0
Extra: 010c6370975225d1e57934cafc6f611e7b112ef23e55a3e09a9004a16da83457bf0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a804f1e9c930f92a1d6eae735dd75a0513e3d767954a5175a5424a717f5887e0 0.000600000000 1693777 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": 1207066, "vin": [ { "gen": { "height": 1207056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a804f1e9c930f92a1d6eae735dd75a0513e3d767954a5175a5424a717f5887e0" } } ], "extra": [ 1, 12, 99, 112, 151, 82, 37, 209, 229, 121, 52, 202, 252, 111, 97, 30, 123, 17, 46, 242, 62, 85, 163, 224, 154, 144, 4, 161, 109, 168, 52, 87, 191, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: