Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a46a09930a49d4f4b928d4f3dc140df032f432986b6d39e3b8a726e96b4295c

Tx prefix hash: 4808fba96bc5239599c745e267543ad3472468603863cba701252212f6398494
Tx public key: 0dc0ccaed77442b4a323570101b6b6f9b3c24c2ed2052f25042acafb1b713ad3
Timestamp: 1582105717 Timestamp [UTC]: 2020-02-19 09:48:37 Age [y:d:h:m:s]: 06:023:00:44:23
Block: 68068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1428087 RingCT/type: yes/0
Extra: 010dc0ccaed77442b4a323570101b6b6f9b3c24c2ed2052f25042acafb1b713ad302110000000cd81c26c0000000000000000000

1 output(s) for total of 0.365143241096 xmr

stealth address amount amount idx tag
00: c47c1c16b3543e414f683676ec1e1a3520b4fc8a9b8353f667a7cd75ee54391b 0.365143241096 125418 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": 68078, "vin": [ { "gen": { "height": 68068 } } ], "vout": [ { "amount": 365143241096, "target": { "key": "c47c1c16b3543e414f683676ec1e1a3520b4fc8a9b8353f667a7cd75ee54391b" } } ], "extra": [ 1, 13, 192, 204, 174, 215, 116, 66, 180, 163, 35, 87, 1, 1, 182, 182, 249, 179, 194, 76, 46, 210, 5, 47, 37, 4, 42, 202, 251, 27, 113, 58, 211, 2, 17, 0, 0, 0, 12, 216, 28, 38, 192, 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) | dinastycoin version: tesla-369