Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adec3facfc61f722c5e62f093a87718189c4fa3379ccf18140ae000aa4321bdf

Tx prefix hash: 9beb75ff18699bb76f0534a09024d798809387f88e929ebf643d6f87c573c231
Tx public key: 16a94b95263962f61a4534ec05ef8e0d7ef86a977bc5e377bdaa86ee9fe51fde
Timestamp: 1574948017 Timestamp [UTC]: 2019-11-28 13:33:37 Age [y:d:h:m:s]: 06:299:11:39:40
Block: 19036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1621698 RingCT/type: yes/0
Extra: 0116a94b95263962f61a4534ec05ef8e0d7ef86a977bc5e377bdaa86ee9fe51fde021100000001ad433a0b000000000000000000

1 output(s) for total of 0.530794859193 xmr

stealth address amount amount idx tag
00: 798579e1eb7d5c320b4f9b226e1d6bb4b7ab844589fc68ab3366661571b1edd2 0.530794859193 29819 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": 19046, "vin": [ { "gen": { "height": 19036 } } ], "vout": [ { "amount": 530794859193, "target": { "key": "798579e1eb7d5c320b4f9b226e1d6bb4b7ab844589fc68ab3366661571b1edd2" } } ], "extra": [ 1, 22, 169, 75, 149, 38, 57, 98, 246, 26, 69, 52, 236, 5, 239, 142, 13, 126, 248, 106, 151, 123, 197, 227, 119, 189, 170, 134, 238, 159, 229, 31, 222, 2, 17, 0, 0, 0, 1, 173, 67, 58, 11, 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: