← previous blocknext block →recent activity
Analyzing
Block #106,363,041
25 transactions · 23 stateful · 2026-09-20 04:04:10 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.64
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,363,041 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w09w110w211w312w417w518w619w720w824w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
16 touches
28 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
12 touches
15 conflicts
0x357e744f…e15b
0x34b655…2a6f
10 touches
10 conflicts
0x01ab5050…95b8
0x34b655…2a6f
10 touches
10 conflicts
0x574628e9…dcc3
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xc851e4c6…f872
0x34b655…2a6f
8 touches
6 conflicts
0xaffceee4…7d2c
0x34b655…2a6f
8 touches
6 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 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity