← previous blocknext block →recent activity
Analyzing
Block #106,235,552
9 transactions · 9 stateful · 2026-09-19 17:22:37 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,235,552 · 9 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
3w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fc9c747…80f8
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x68a3da5a…f84c
0x34b655…2a6f
4 touches
1 conflict
0x0e0c66fe…796f
0x1e2721…7805
2 touches
0 conflicts
0x27c8497b…dcc4
0x754704…b603
2 touches
0 conflicts
0x431fa96d…6ac0
0x754704…b603
2 touches
0 conflicts
0x63e367c9…b363
0x754704…b603
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 0x8fc9c74709…1180f8
Audit this contract →
← previous block·next block →recent activity