Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2c26b95a812481804f31cffcda96811dcac60f9b8b44322ee9ce66eb729e059

Tx prefix hash: 5e927946402a79a1465a58468f3b87d4a75e31959c79c837101cc6d8e86f4db1
Tx public key: decb40748dfdf27354df57fa7af880e895dffc235172ce778bad205b3135f582
Timestamp: 1615724665 Timestamp [UTC]: 2021-03-14 12:24:25 Age [y:d:h:m:s]: 05:060:03:06:50
Block: 218334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1313863 RingCT/type: yes/0
Extra: 01decb40748dfdf27354df57fa7af880e895dffc235172ce778bad205b3135f5820211000000c03bb2744a000000000000000000

1 output(s) for total of 0.116029767333 xmr

stealth address amount amount idx tag
00: 4db0a1daf8d1e676ae53edf4d05d72a977d0269f9625a513fd9d3f01d286b001 0.116029767333 448634 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": 218344, "vin": [ { "gen": { "height": 218334 } } ], "vout": [ { "amount": 116029767333, "target": { "key": "4db0a1daf8d1e676ae53edf4d05d72a977d0269f9625a513fd9d3f01d286b001" } } ], "extra": [ 1, 222, 203, 64, 116, 141, 253, 242, 115, 84, 223, 87, 250, 122, 248, 128, 232, 149, 223, 252, 35, 81, 114, 206, 119, 139, 173, 32, 91, 49, 53, 245, 130, 2, 17, 0, 0, 0, 192, 59, 178, 116, 74, 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: