← previous blocknext block →recent activity
Analyzing
Block #99,959,290
20 transactions · 17 stateful · 2026-08-28 17:35:19 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,959,290 · 20 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
6w07w110w211w314w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a548af5…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0x75d5f8d3…f860
0x34b655…2a6f
4 touches
1 conflict
0x8c17951e…38fd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
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 0x5a548af508…f00eb0
Audit this contract →
← previous block·next block →recent activity