← previous blocknext block →recent activity
Analyzing
Block #99,958,660
22 transactions · 18 stateful · 2026-08-28 17:32:09 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,958,660 · 22 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
8w013w114w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x753223d5…c783
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfc2493d3…6898
0x34b655…2a6f
4 touches
1 conflict
0xfd7f5b55…4994
0x34b655…2a6f
4 touches
1 conflict
0x290abc80…f605
0x34b655…2a6f
4 touches
1 conflict
0x3e4cf98e…4594
0x34b655…2a6f
4 touches
1 conflict
0xf00d2133…d68e
0x754704…b603
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
1 conflict on slot 0x753223d5b3…01c783
Audit this contract →
← previous block·next block →recent activity