Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc6e173b56a27a00f87c773841e4cfe9dd72448ddb42c3d49971ed0437918e23

Tx prefix hash: 94061e44f0095a8d26dce645bc938343b596d095ef9973af6d0f4dd3e0d46559
Tx public key: a57e02b94d3679ea72d7558e2cc75f9823a45a3b0351cc1ff8bd078f283087a0
Timestamp: 1578631190 Timestamp [UTC]: 2020-01-10 04:39:50 Age [y:d:h:m:s]: 06:258:07:37:00
Block: 42210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1599596 RingCT/type: yes/0
Extra: 01a57e02b94d3679ea72d7558e2cc75f9823a45a3b0351cc1ff8bd078f283087a002110000000d8a2ee0d9000000000000000000

1 output(s) for total of 0.444776253376 xmr

stealth address amount amount idx tag
00: 1e1f4f58fb7a47e9bda8f36f1a57ecc773627cf558e2329deebbbb03aac89cd3 0.444776253376 75946 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": 42220, "vin": [ { "gen": { "height": 42210 } } ], "vout": [ { "amount": 444776253376, "target": { "key": "1e1f4f58fb7a47e9bda8f36f1a57ecc773627cf558e2329deebbbb03aac89cd3" } } ], "extra": [ 1, 165, 126, 2, 185, 77, 54, 121, 234, 114, 215, 85, 142, 44, 199, 95, 152, 35, 164, 90, 59, 3, 81, 204, 31, 248, 189, 7, 143, 40, 48, 135, 160, 2, 17, 0, 0, 0, 13, 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: