← previous blocknext block →recent activity
Analyzing
Block #106,190,777
39 transactions · 37 stateful · 2026-09-19 13:37:10 UTC
Parallelism
56/100
Blocked
62%
Avg conflicts / tx
3.67
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,190,777 · 39 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w214w315w417w519w620w722w823w924w1025w1126w1227w1328w1429w1538w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd62f3741…b903
0x34b655…2a6f
28 touches
91 conflicts
0xc824469a…6425
0x34b655…2a6f
28 touches
91 conflicts
0xe33beb97…6c6f
0x34b655…2a6f
22 touches
55 conflicts
0x315e07b8…9823
0x34b655…2a6f
12 touches
15 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x35eafbad…52ca
0x34b655…2a6f
8 touches
6 conflicts
0xd79b9dc6…1e74
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
91 conflicts on slot 0xd62f374157…55b903
Audit this contract →
← previous block·next block →recent activity