← previous blocknext block →recent activity
Analyzing
Block #106,207,045
17 transactions · 17 stateful · 2026-09-19 14:59:05 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,207,045 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w011w112w213w314w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0a4e112…f855
0x34b655…2a6f
10 touches
10 conflicts
0x994033ea…4aba
0x34b655…2a6f
8 touches
6 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x7eb82f85…2b53
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
10 conflicts on slot 0xb0a4e112ff…8cf855
Audit this contract →
← previous block·next block →recent activity