← previous blocknext block →recent activity
Analyzing
Block #93,372,048
31 transactions · 25 stateful · 2026-08-05 14:34:18 UTC
Parallelism
74/100
Blocked
64%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,372,048 · 31 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
1w02w13w24w05w16w27w38w49w010w119w020w021w122w523w324w425w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x1a287886…0266
0xa6afd3…d132
8 touches
6 conflicts
0x53e50026…6d8c
0x2b46c0…1669
6 touches
3 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0x213ee207…a151
0x2b46c0…1669
6 touches
3 conflicts
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: 0x40c49f17…d22af0
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity