Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c6efe7d5bea87adf34cd5fcf90209f31a9bc140c2bb37c46b0c58ad2ac8206a

Tx prefix hash: 6a2599f7a0b9ac4470f5a91d2e3122bda2ac79ef0d27dae5e4c279f39ff60c78
Tx public key: b066c89092ed6e37a6408ce1aadd04ecae1e582dd915529c31655177bd12de9a
Timestamp: 1583457419 Timestamp [UTC]: 2020-03-06 01:16:59 Age [y:d:h:m:s]: 06:072:22:43:17
Block: 77223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1458243 RingCT/type: yes/0
Extra: 01b066c89092ed6e37a6408ce1aadd04ecae1e582dd915529c31655177bd12de9a02110000000b56c366d3000000000000000000

1 output(s) for total of 0.340509268911 xmr

stealth address amount amount idx tag
00: 9e0e5f39f3cc2fc530b77105abbd9a816d8c3490d6e88f7819fe50f0b2c88853 0.340509268911 142110 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": 77233, "vin": [ { "gen": { "height": 77223 } } ], "vout": [ { "amount": 340509268911, "target": { "key": "9e0e5f39f3cc2fc530b77105abbd9a816d8c3490d6e88f7819fe50f0b2c88853" } } ], "extra": [ 1, 176, 102, 200, 144, 146, 237, 110, 55, 166, 64, 140, 225, 170, 221, 4, 236, 174, 30, 88, 45, 217, 21, 82, 156, 49, 101, 81, 119, 189, 18, 222, 154, 2, 17, 0, 0, 0, 11, 86, 195, 102, 211, 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: