← previous blocknext block →recent activity
Analyzing
Block #94,961,174
21 transactions · 21 stateful · 2026-08-11 04:03:42 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,961,174 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w19w210w212w013w114w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x54734133…fb61
0x34b655…2a6f
4 touches
1 conflict
0x56bb67c6…0abf
0x065c9d…c394
4 touches
1 conflict
0xba3d433b…e905
0x34b655…2a6f
4 touches
1 conflict
0xe52da074…4dc0
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
3 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity