← previous blocknext block →recent activity
Analyzing
Block #106,946,603
28 transactions · 22 stateful · 2026-09-22 05:02:18 UTC
Parallelism
89/100
Blocked
41%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,946,603 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w28w09w110w211w018w121w023w025w126w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54439e7a…8c34
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x858e40c0…7e30
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3f2168b4…37b5
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
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
3 conflicts on slot 0x54439e7ac5…048c34
Audit this contract →
← previous block·next block →recent activity