← previous blocknext block →recent activity
Analyzing
Block #99,958,704
17 transactions · 16 stateful · 2026-08-28 17:32:22 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,958,704 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w07w08w19w110w011w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5cf29ef…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x36f63e4f…f319
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0xfd7f5b55…4994
0x34b655…2a6f
4 touches
1 conflict
0xfc2493d3…6898
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
3 conflicts on slot 0xb5cf29efbf…80e5f1
Audit this contract →
← previous block·next block →recent activity