← previous blocknext block →recent activity
Analyzing
Block #99,960,520
23 transactions · 23 stateful · 2026-08-28 17:41:31 UTC
Parallelism
87/100
Blocked
39%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,960,520 · 23 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
1w04w16w17w28w09w110w012w115w117w220w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24bb46f7…3853
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5f4b1c7a…fa1c
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x059d1c22…d4f3
0x34b655…2a6f
4 touches
1 conflict
0x1408a100…f721
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 0x24bb46f739…c13853
Audit this contract →
← previous block·next block →recent activity