← previous blocknext block →recent activity
Analyzing
Block #99,271,183
19 transactions · 17 stateful · 2026-08-26 07:37:48 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,271,183 · 19 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
1w04w15w212w213w014w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b2b7213…4899
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4527fb58…5992
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x03a0038a…98c8
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
2 touches
0 conflicts
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 0x8b2b72134b…a34899
Audit this contract →
← previous block·next block →recent activity