← previous blocknext block →recent activity
Analyzing
Block #99,870,631
15 transactions · 15 stateful · 2026-08-28 10:08:32 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,870,631 · 15 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
2w03w14w25w06w18w29w310w411w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x68dfc6ca…56ac
0x34b655…2a6f
8 touches
6 conflicts
0x295780b7…d2d1
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0xdfb9a93d…699a
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity