← previous blocknext block →recent activity
Analyzing
Block #105,682,839
20 transactions · 17 stateful · 2026-09-17 18:58:21 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,682,839 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w110w211w312w413w516w218w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x88e92ec7…696d
0x34b655…2a6f
8 touches
6 conflicts
0x429c8b35…0f5c
0x34b655…2a6f
6 touches
3 conflicts
0x4dd90e21…5694
0x34b655…2a6f
6 touches
3 conflicts
0x8ed2a645…b3ce
0x34b655…2a6f
6 touches
3 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 conflicts
0x3d93ad2c…e747
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
15 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity