Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f1f0232bbbdb866a38590744da91ba40ab56b92b8753595be1d3825b9fd8d2a

Tx prefix hash: fde33a05acf43cda38cac36d56a74a5a00947218b8fdf609887f20e790ea1dd7
Tx public key: dd68cb66762fb3e182fbee2bf3c26c31591b9e0bb7759cd0f37425cec994477a
Timestamp: 1716071763 Timestamp [UTC]: 2024-05-18 22:36:03 Age [y:d:h:m:s]: 02:184:18:11:49
Block: 1024985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 657039 RingCT/type: yes/0
Extra: 01dd68cb66762fb3e182fbee2bf3c26c31591b9e0bb7759cd0f37425cec994477a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e047de6f9062c545584c14e3c3fd74443c6ea8fd0df11acc1995ba0e94457fdf 0.000600000000 1491158 of 15 -

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": 1024995, "vin": [ { "gen": { "height": 1024985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e047de6f9062c545584c14e3c3fd74443c6ea8fd0df11acc1995ba0e94457fdf" } } ], "extra": [ 1, 221, 104, 203, 102, 118, 47, 179, 225, 130, 251, 238, 43, 243, 194, 108, 49, 89, 27, 158, 11, 183, 117, 156, 208, 243, 116, 37, 206, 201, 148, 71, 122, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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: