← previous blocknext block →recent activity
Analyzing
Block #99,935,505
11 transactions · 10 stateful · 2026-08-28 15:35:27 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,935,505 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0004b1fc…36b1
0x34b655…2a6f
4 touches
1 conflict
0x4a45b318…9716
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x0acf8ab1…508e
0x34b655…2a6f
2 touches
0 conflicts
0x256341f6…89e9
0x34b655…2a6f
2 touches
0 conflicts
0x295780b7…d2d1
0x34b655…2a6f
2 touches
0 conflicts
0x30056d3a…13ad
0x34b655…2a6f
2 touches
0 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x0004b1fc86…5136b1
Audit this contract →
← previous block·next block →recent activity