Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 250049e0cc3f4475df3ec4bf29d269672e700148ea80e13f3b58e6041c55c28b

Tx prefix hash: ab04a5c7af004e3280d92a86b4ec6c53d27da440213c8eafa13d17cbce885739
Tx public key: 62bc81504834f50ea599259c4f6460048743caa7eca87caf4cbb865321ef3179
Timestamp: 1578832841 Timestamp [UTC]: 2020-01-12 12:40:41 Age [y:d:h:m:s]: 06:130:01:14:54
Block: 43957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1495081 RingCT/type: yes/0
Extra: 0162bc81504834f50ea599259c4f6460048743caa7eca87caf4cbb865321ef31790211000000eebd0f9f9f000000000000000000

1 output(s) for total of 0.438887339907 xmr

stealth address amount amount idx tag
00: 762cc249618547b56d74f498e50e430becdf68e92a13ce1ff470c97b332548a7 0.438887339907 79806 of 0 -

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": 43967, "vin": [ { "gen": { "height": 43957 } } ], "vout": [ { "amount": 438887339907, "target": { "key": "762cc249618547b56d74f498e50e430becdf68e92a13ce1ff470c97b332548a7" } } ], "extra": [ 1, 98, 188, 129, 80, 72, 52, 245, 14, 165, 153, 37, 156, 79, 100, 96, 4, 135, 67, 202, 167, 236, 168, 124, 175, 76, 187, 134, 83, 33, 239, 49, 121, 2, 17, 0, 0, 0, 238, 189, 15, 159, 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: