Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b89a3daea0346ccdad066578520efdb3fa8d8732849a6dfd7cb37d0bef63f7d

Tx prefix hash: 31fd0c1c9868fd92e324b323bbd7f200a354fa3a8802ee60ce0c95770a4a5ce6
Tx public key: 3fa11735d4e2208378a71e57caf88440cc4d90ae4b98f5fbc3f79cf6fb1b0694
Timestamp: 1773114390 Timestamp [UTC]: 2026-03-10 03:46:30 Age [y:d:h:m:s]: 00:249:17:53:09
Block: 1494517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183907 RingCT/type: yes/0
Extra: 013fa11735d4e2208378a71e57caf88440cc4d90ae4b98f5fbc3f79cf6fb1b0694021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d05cd3a779b8b91011962a93ac76d6bd1fe35232b099f271ceb0f8caad8d90e5 0.000600000000 1984089 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": 1494527, "vin": [ { "gen": { "height": 1494517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d05cd3a779b8b91011962a93ac76d6bd1fe35232b099f271ceb0f8caad8d90e5" } } ], "extra": [ 1, 63, 161, 23, 53, 212, 226, 32, 131, 120, 167, 30, 87, 202, 248, 132, 64, 204, 77, 144, 174, 75, 152, 245, 251, 195, 247, 156, 246, 251, 27, 6, 148, 2, 17, 0, 0, 0, 5, 228, 245, 25, 63, 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: