← previous blocknext block →recent activity
Analyzing
Block #99,443,696
26 transactions · 22 stateful · 2026-08-26 22:06:14 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,443,696 · 26 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
3w04w15w06w17w18w29w311w212w220w024w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676207a8…5d7e
0x34b655…2a6f
8 touches
6 conflicts
0x733c7779…a647
0x34b655…2a6f
6 touches
3 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x1646cca5…971e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd0f6f4f2…dffa
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 0x676207a88a…e05d7e
Audit this contract →
← previous block·next block →recent activity