← previous blocknext block →recent activity
Analyzing
Block #106,917,877
22 transactions · 22 stateful · 2026-09-22 02:37:43 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,917,877 · 22 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
1w03w15w28w09w110w211w316w417w518w620w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49acf7ff…912d
0x34b655…2a6f
14 touches
21 conflicts
0x518221db…65f7
0x34b655…2a6f
10 touches
10 conflicts
0x4786839b…c29a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x469dac8d…3411
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0xc35d158c…6271
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
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
21 conflicts on slot 0x49acf7ffd5…4b912d
Audit this contract →
← previous block·next block →recent activity