← previous blocknext block →recent activity
Analyzing
Block #99,187,253
23 transactions · 22 stateful · 2026-08-26 00:35:26 UTC
Parallelism
78/100
Blocked
32%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,187,253 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w09w010w111w113w215w316w217w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbae3502c…9836
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x641aed07…bcb9
0x34b655…2a6f
6 touches
3 conflicts
0x9482a067…eba9
0x34b655…2a6f
6 touches
3 conflicts
0x45ac4d52…cacb
0x34b655…2a6f
4 touches
1 conflict
0x46483cb1…e7ca
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
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 0xbae3502c1e…739836
Audit this contract →
← previous block·next block →recent activity