← previous blocknext block →recent activity
Analyzing
Block #92,483,334
19 transactions · 18 stateful · 2026-08-02 12:01:46 UTC
Parallelism
58/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,483,334 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w28w19w010w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x5890dedf…54c9
0x34b655…2a6f
7 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x4bc1abab…5874
0x34b655…2a6f
5 touches
3 conflicts
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
10 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity