← previous blocknext block →recent activity
Analyzing
Block #99,097,782
14 transactions · 14 stateful · 2026-08-25 17:05:14 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,097,782 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe770323…579f
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x3a08dbb9…8750
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x5d0464f2…4110
0x34b655…2a6f
4 touches
1 conflict
0xce60df54…c3e8
0x34b655…2a6f
4 touches
1 conflict
0xd2dfd9bc…3eec
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
1 conflict on slot 0xfe77032353…b7579f
Audit this contract →
← previous block·next block →recent activity