← previous blocknext block →recent activity
Analyzing
Block #94,306,508
10 transactions · 10 stateful · 2026-08-08 21:00:45 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,306,508 · 10 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
1w02w13w04w16w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0x0725ad1d…a03f
0x34b655…2a6f
4 touches
1 conflict
0x0960ac51…5440
0x34b655…2a6f
4 touches
1 conflict
0x1279ed80…4a27
0x34b655…2a6f
4 touches
1 conflict
0x8de38574…ad6e
0x34b655…2a6f
4 touches
1 conflict
0xe6043046…5757
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
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 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity