← previous blocknext block →recent activity
Analyzing
Block #106,389,152
32 transactions · 30 stateful · 2026-09-20 06:15:35 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,389,152 · 32 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w316w417w521w522w625w729w630w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba33378a…f1df
0x34b655…2a6f
14 touches
21 conflicts
0x9ca9fcbb…3982
0x34b655…2a6f
12 touches
15 conflicts
0xfaee4f79…d6ee
0x34b655…2a6f
10 touches
10 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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 0xba33378abc…73f1df
Audit this contract →
← previous block·next block →recent activity