← previous blocknext block →recent activity
Analyzing
Block #106,555,990
30 transactions · 29 stateful · 2026-09-20 20:15:17 UTC
Parallelism
53/100
Blocked
59%
Avg conflicts / tx
2.6
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,555,990 · 30 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w19w012w213w314w415w516w617w718w819w820w921w1022w1123w1224w1329w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4330eac7…eddb
0x34b655…2a6f
18 touches
36 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
14 touches
21 conflicts
0x32aab5b0…0e4f
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0x810a3aa2…0227
0x34b655…2a6f
12 touches
15 conflicts
0x646dd8ae…60c5
0x34b655…2a6f
12 touches
15 conflicts
0x0463db49…5d05
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0x4330eac72b…b9eddb
Audit this contract →
← previous block·next block →recent activity