Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bc011f3d9573abc8346275a1f81b099f2a80bc3a5f8620a577ae3164a3da040

Tx prefix hash: e2e6a8bcf7bdb8f190b8ce60595b7001313ae16945bbd8df37e159d314c9855c
Tx public key: 4fa06d966c4a8cffa7d7142dd445a8cc13ca3de063c76f1f1cd6759daa635040
Timestamp: 1643305835 Timestamp [UTC]: 2022-01-27 17:50:35 Age [y:d:h:m:s]: 04:299:19:46:02
Block: 426498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1256996 RingCT/type: yes/0
Extra: 014fa06d966c4a8cffa7d7142dd445a8cc13ca3de063c76f1f1cd6759daa63504002110000001ddb0c7f64000000000000000000

1 output(s) for total of 0.023704750657 xmr

stealth address amount amount idx tag
00: 6d38c0edf8fc0c641523728eab8303920ef8cb16a53cdeca5d82ddd1a346273e 0.023704750657 835337 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": 426508, "vin": [ { "gen": { "height": 426498 } } ], "vout": [ { "amount": 23704750657, "target": { "key": "6d38c0edf8fc0c641523728eab8303920ef8cb16a53cdeca5d82ddd1a346273e" } } ], "extra": [ 1, 79, 160, 109, 150, 108, 74, 140, 255, 167, 215, 20, 45, 212, 69, 168, 204, 19, 202, 61, 224, 99, 199, 111, 31, 28, 214, 117, 157, 170, 99, 80, 64, 2, 17, 0, 0, 0, 29, 219, 12, 127, 100, 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: