← previous blocknext block →recent activity
Analyzing
Block #99,255,185
27 transactions · 22 stateful · 2026-08-26 06:17:14 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,255,185 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w210w211w113w316w322w023w125w026w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe720d1f0…f726
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xab60dc09…85e4
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x9212cb48…5e05
0x065c9d…c394
5 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0xe720d1f0b8…c5f726
Audit this contract →
← previous block·next block →recent activity