← previous blocknext block →recent activity
Analyzing
Block #106,916,741
24 transactions · 23 stateful · 2026-09-22 02:32:00 UTC
Parallelism
58/100
Blocked
48%
Avg conflicts / tx
1.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,916,741 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w410w512w613w714w815w923w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x4996be87…663a
0x34b655…2a6f
12 touches
15 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
10 touches
10 conflicts
0xd9545ad3…62ea
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x3d2785ea…dd64
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
21 conflicts on slot 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity