← previous blocknext block →recent activity
Analyzing
Block #99,976,778
12 transactions · 12 stateful · 2026-08-28 19:03:24 UTC
Parallelism
42/100
Blocked
58%
Avg conflicts / tx
2.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,976,778 · 12 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
10 touches
10 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
10 touches
10 conflicts
0xbd590df7…9891
0x34b655…2a6f
10 touches
10 conflicts
0x1bec765d…70c6
0x34b655…2a6f
5 touches
3 conflicts
0x7083c381…0ce7
0x34b655…2a6f
4 touches
1 conflict
0x7a32f943…e6f4
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
21 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity