← previous blocknext block →recent activity
Analyzing
Block #99,252,879
9 transactions · 9 stateful · 2026-08-26 06:05:37 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,252,879 · 9 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
1w04w15w26w38w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x793357cd…1653
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
6 touches
3 conflicts
0x7ad9dc5b…278c
0x34b655…2a6f
6 touches
3 conflicts
0xfc0a827d…71e0
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x2caeb7f5…b6bb
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 0x793357cdaa…211653
Audit this contract →
← previous block·next block →recent activity