← previous blocknext block →recent activity
Analyzing
Block #106,216,132
16 transactions · 14 stateful · 2026-09-19 15:44:49 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,216,132 · 16 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
1w06w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73b87bc2…457a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0c8cf7ab…e651
0x34b655…2a6f
2 touches
0 conflicts
0x0df41391…30a8
0x34b655…2a6f
2 touches
0 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x68a56edb…36ac
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 0x73b87bc243…9c457a
Audit this contract →
← previous block·next block →recent activity