Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80dae9c89f1ff5e97bca0377c04918fd2f64b0ed558b0ca843fab1cb00bc6ff0

Tx prefix hash: 1efdcd88343691e3a160a6e1434bd151c36f8b39094410644b9b6abe0f402ecd
Tx public key: 86d658c871834287cf97de711ff4f9cd8a0e4830c7fde3f337892c673d334827
Timestamp: 1604482550 Timestamp [UTC]: 2020-11-04 09:35:50 Age [y:d:h:m:s]: 06:016:15:14:32
Block: 145750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1536527 RingCT/type: yes/0
Extra: 0186d658c871834287cf97de711ff4f9cd8a0e4830c7fde3f337892c673d334827021100000035f4b4cc44000000000000000000

1 output(s) for total of 0.201869377236 xmr

stealth address amount amount idx tag
00: c6f3f8b3f2c793e1dfb853cccc887e9a8d93507572b2bf5b1f3e45e2b34afb97 0.201869377236 242266 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": 145760, "vin": [ { "gen": { "height": 145750 } } ], "vout": [ { "amount": 201869377236, "target": { "key": "c6f3f8b3f2c793e1dfb853cccc887e9a8d93507572b2bf5b1f3e45e2b34afb97" } } ], "extra": [ 1, 134, 214, 88, 200, 113, 131, 66, 135, 207, 151, 222, 113, 31, 244, 249, 205, 138, 14, 72, 48, 199, 253, 227, 243, 55, 137, 44, 103, 61, 51, 72, 39, 2, 17, 0, 0, 0, 53, 244, 180, 204, 68, 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: