← previous blocknext block →recent activity
Analyzing
Block #94,196,832
39 transactions · 37 stateful · 2026-08-08 11:45:03 UTC
Parallelism
92/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,196,832 · 39 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w010w136w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b89ce6f…cc35
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x12d867cc…b97c
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
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
1 conflict on slot 0x6b89ce6fa0…95cc35
Audit this contract →
← previous block·next block →recent activity