← previous blocknext block →recent activity
Analyzing
Block #106,457,040
29 transactions · 27 stateful · 2026-09-20 11:57:18 UTC
Parallelism
62/100
Blocked
70%
Avg conflicts / tx
1.93
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,457,040 · 29 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w27w310w314w416w117w218w519w620w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2836d18c…d85c
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
8 touches
6 conflicts
0x364036f4…10de
0x34b655…2a6f
8 touches
6 conflicts
0x159cff26…7665
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x2836d18c0d…0dd85c
Audit this contract →
← previous block·next block →recent activity