Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82852780ca242e3db22ea353d3b4f567bbaa642f17525e0615db47202bd65dae

Tx prefix hash: 64ff5d46d4d362e6617058b02b6041c95e6c93b17371a1eb4cf28f42102204a6
Tx public key: 50440b3e46511715f6c643aff50ceedd2a1da91dcda3ea436ed0570a6504dece
Timestamp: 1644471021 Timestamp [UTC]: 2022-02-10 05:30:21 Age [y:d:h:m:s]: 04:099:01:04:27
Block: 435481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1102580 RingCT/type: yes/0
Extra: 0150440b3e46511715f6c643aff50ceedd2a1da91dcda3ea436ed0570a6504dece02110000000e06faf294000000000000000000

1 output(s) for total of 0.022134563923 xmr

stealth address amount amount idx tag
00: 7c110daed4b28ac97b6bc1f3f178f5ddb82c9a62e0a47c5914e32a3f7e42d288 0.022134563923 846680 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": 435491, "vin": [ { "gen": { "height": 435481 } } ], "vout": [ { "amount": 22134563923, "target": { "key": "7c110daed4b28ac97b6bc1f3f178f5ddb82c9a62e0a47c5914e32a3f7e42d288" } } ], "extra": [ 1, 80, 68, 11, 62, 70, 81, 23, 21, 246, 198, 67, 175, 245, 12, 238, 221, 42, 29, 169, 29, 205, 163, 234, 67, 110, 208, 87, 10, 101, 4, 222, 206, 2, 17, 0, 0, 0, 14, 6, 250, 242, 148, 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: