Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3023fa2c69e23543a1c73d1ea90c774c79198b9ce86668e125cd846949a1c1db

Tx prefix hash: 0d9eb27aa2b518c3d44b76e9a01e4cd05472c5bb60713c16e318e7b7348d0115
Tx public key: f2ef3c2d8f8eac1e9314512ec704be326c709447bdd039387d879b792e817b3d
Timestamp: 1577200214 Timestamp [UTC]: 2019-12-24 15:10:14 Age [y:d:h:m:s]: 06:271:21:52:58
Block: 30810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1608847 RingCT/type: yes/0
Extra: 01f2ef3c2d8f8eac1e9314512ec704be326c709447bdd039387d879b792e817b3d0211000000038a2ee0d9000000000000000000

1 output(s) for total of 0.485193016415 xmr

stealth address amount amount idx tag
00: 94fe85b769354f088614852c8b9de42d110cf7e6e72b099bf2fe91a533009f0c 0.485193016415 50860 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": 30820, "vin": [ { "gen": { "height": 30810 } } ], "vout": [ { "amount": 485193016415, "target": { "key": "94fe85b769354f088614852c8b9de42d110cf7e6e72b099bf2fe91a533009f0c" } } ], "extra": [ 1, 242, 239, 60, 45, 143, 142, 172, 30, 147, 20, 81, 46, 199, 4, 190, 50, 108, 112, 148, 71, 189, 208, 57, 56, 125, 135, 155, 121, 46, 129, 123, 61, 2, 17, 0, 0, 0, 3, 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: