Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3e07626fd9b8b256b026b6a98d5738000a9c1dfd3f59ef80b4409c5749f5aa5

Tx prefix hash: a17c8e0c9e49e68947f5f583bccd0cc250770c7d480245e9f8d66453b733c2a5
Tx public key: a6047bfe104792e201ff22c57a6a88d2acbbe922273ef611d3e72fbe6046551b
Timestamp: 1693880567 Timestamp [UTC]: 2023-09-05 02:22:47 Age [y:d:h:m:s]: 03:076:05:06:35
Block: 841195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 840527 RingCT/type: yes/0
Extra: 01a6047bfe104792e201ff22c57a6a88d2acbbe922273ef611d3e72fbe6046551b02110000000933af99f4000000000000000000

1 output(s) for total of 0.001001778803 xmr

stealth address amount amount idx tag
00: 9383ced92979455beab04759e9960cecd98b36d1ef99cc461246f6f4d9c3c2e0 0.001001778803 1294203 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": 841205, "vin": [ { "gen": { "height": 841195 } } ], "vout": [ { "amount": 1001778803, "target": { "key": "9383ced92979455beab04759e9960cecd98b36d1ef99cc461246f6f4d9c3c2e0" } } ], "extra": [ 1, 166, 4, 123, 254, 16, 71, 146, 226, 1, 255, 34, 197, 122, 106, 136, 210, 172, 187, 233, 34, 39, 62, 246, 17, 211, 231, 47, 190, 96, 70, 85, 27, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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: