← previous blocknext block →recent activity
Analyzing
Block #99,114,643
14 transactions · 13 stateful · 2026-08-25 18:30:02 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,114,643 · 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
1w05w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89fee327…83c4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd26dd791…26fb
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x32287d4a…6699
0x34b655…2a6f
2 touches
0 conflicts
0x7b29c53c…f40f
0x34b655…2a6f
2 touches
0 conflicts
0x7f5b2c1d…0e7f
0x34b655…2a6f
2 touches
0 conflicts
0x8e99ff06…9eb5
0x34b655…2a6f
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 0x89fee327b4…6983c4
Audit this contract →
← previous block·next block →recent activity