← previous blocknext block →recent activity
Analyzing
Block #106,388,958
20 transactions · 19 stateful · 2026-09-20 06:14:37 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
2.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,388,958 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w28w09w112w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3423de1…1ef2
0x34b655…2a6f
16 touches
28 conflicts
0xba33378a…f1df
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0x33365a6a…7e0b
0x34b655…2a6f
8 touches
6 conflicts
0x8d175439…fb79
0x34b655…2a6f
6 touches
3 conflicts
0xd79b9dc6…1e74
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
28 conflicts on slot 0xa3423de162…bf1ef2
Audit this contract →
← previous block·next block →recent activity