← previous blocknext block →recent activity
Analyzing
Block #99,980,922
15 transactions · 15 stateful · 2026-08-28 19:24:16 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,980,922 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w211w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0xf95c3143…ac6d
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xff7cb355…3404
0x34b655…2a6f
6 touches
3 conflicts
0x42e917f7…ed8c
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0x974e6bfb…8a22
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity