← previous blocknext block →recent activity
Analyzing
Block #99,037,187
18 transactions · 16 stateful · 2026-08-25 11:56:45 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,037,187 · 18 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
1w04w05w16w17w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d75a923…c236
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x820d7282…6c34
0x34b655…2a6f
6 touches
3 conflicts
0x3153cb27…825c
0x34b655…2a6f
6 touches
3 conflicts
0xc4e19ae4…0788
0xe7cd86…c82d
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x95a5ab92…3a8a
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
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 0x2d75a923d2…b2c236
Audit this contract →
← previous block·next block →recent activity