← previous blocknext block →recent activity
Analyzing
Block #106,428,264
17 transactions · 17 stateful · 2026-09-20 09:32:24 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,428,264 · 17 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
1w02w110w011w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2dc3fdf…6de9
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x5b17b0ae…fccf
0x34b655…2a6f
4 touches
1 conflict
0x0bd2fd64…69d4
0x34b655…2a6f
4 touches
1 conflict
0x8d664414…3344
0x34b655…2a6f
4 touches
1 conflict
0x5ce28434…11ee
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 0xa2dc3fdfe9…356de9
Audit this contract →
← previous block·next block →recent activity