← previous blocknext block →recent activity
Analyzing
Block #99,076,734
17 transactions · 17 stateful · 2026-08-25 15:19:00 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,076,734 · 17 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
2w03w15w09w110w211w313w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad4e90b…33a5
0x34b655…2a6f
8 touches
6 conflicts
0x0b3eb43a…ca08
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x62d1c3b2…c1f6
0x34b655…2a6f
4 touches
1 conflict
0xb2d8af24…4750
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xe2fa91e6…44f7
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
6 conflicts on slot 0xbad4e90ba6…2233a5
Audit this contract →
← previous block·next block →recent activity