← previous blocknext block →recent activity
Analyzing
Block #106,200,290
11 transactions · 10 stateful · 2026-09-19 14:25:02 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,200,290 · 11 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
6w07w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5780e2ab…1e3b
0x34b655…2a6f
4 touches
1 conflict
0x0de7749d…5bef
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0xf1564b2b…970b
0x34b655…2a6f
4 touches
1 conflict
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0xf21aea2f…dab9
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
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
1 conflict on slot 0x5780e2abb3…d31e3b
Audit this contract →
← previous block·next block →recent activity