Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc1d66b932ef3d9a45e4d1cb6ecef7c00eadc645934f3c1b2def963b34976151

Tx prefix hash: 4281a1534b1022ef846cd97cdf6ca5b9dbe42bdc3d00a00585fa18b4497ee49d
Tx public key: 8e106ae580b564eae39d13f78194d146c527ee1eb94b379ff43dd84c242b3cb5
Timestamp: 1605660785 Timestamp [UTC]: 2020-11-18 00:53:05 Age [y:d:h:m:s]: 05:311:19:23:59
Block: 149077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1493700 RingCT/type: yes/0
Extra: 018e106ae580b564eae39d13f78194d146c527ee1eb94b379ff43dd84c242b3cb502110000029ca45716b1000000000000000000

1 output(s) for total of 0.196822315613 xmr

stealth address amount amount idx tag
00: b06ff3e4ab9cfef75e2bb727ff5648778e6381b0303536d66be92b0834bb05fe 0.196822315613 247913 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": 149087, "vin": [ { "gen": { "height": 149077 } } ], "vout": [ { "amount": 196822315613, "target": { "key": "b06ff3e4ab9cfef75e2bb727ff5648778e6381b0303536d66be92b0834bb05fe" } } ], "extra": [ 1, 142, 16, 106, 229, 128, 181, 100, 234, 227, 157, 19, 247, 129, 148, 209, 70, 197, 39, 238, 30, 185, 75, 55, 159, 244, 61, 216, 76, 36, 43, 60, 181, 2, 17, 0, 0, 2, 156, 164, 87, 22, 177, 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: