← previous blocknext block →recent activity
Analyzing
Block #106,950,857
15 transactions · 15 stateful · 2026-09-22 05:23:43 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,950,857 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x1f396cee…862f
0x34b655…2a6f
6 touches
3 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xa405b948…9966
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x4c517c5d…851c
0x34b655…2a6f
4 touches
1 conflict
0x66cc1603…a103
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
3 conflicts on slot 0xe22ab637d9…007a8e
Audit this contract →
← previous block·next block →recent activity