Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecf2f1a323500c0de0da14e617a1b1d42974e6d741e7890d01a33ee887e1bb06

Tx prefix hash: ef75bfab5b5009624062ac276cdccb4ee999b85338a40cd9590539518fee0fe0
Tx public key: 068cab8937428aac6a71e2ef5797f9ea4f41e15b07c07ef318e9730f0a739617
Timestamp: 1581659951 Timestamp [UTC]: 2020-02-14 05:59:11 Age [y:d:h:m:s]: 06:282:08:48:11
Block: 64646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1618831 RingCT/type: yes/0
Extra: 01068cab8937428aac6a71e2ef5797f9ea4f41e15b07c07ef318e9730f0a7396170211000000138a2ee0d9000000000000000000

1 output(s) for total of 0.374801894721 xmr

stealth address amount amount idx tag
00: dbc71d8d2add336e04cb78859d29531307cfcf507c6dea6478c8525ddc1b2ed6 0.374801894721 119257 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": 64656, "vin": [ { "gen": { "height": 64646 } } ], "vout": [ { "amount": 374801894721, "target": { "key": "dbc71d8d2add336e04cb78859d29531307cfcf507c6dea6478c8525ddc1b2ed6" } } ], "extra": [ 1, 6, 140, 171, 137, 55, 66, 138, 172, 106, 113, 226, 239, 87, 151, 249, 234, 79, 65, 225, 91, 7, 192, 126, 243, 24, 233, 115, 15, 10, 115, 150, 23, 2, 17, 0, 0, 0, 19, 138, 46, 224, 217, 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: