← previous blocknext block →recent activity
Analyzing
Block #106,372,750
16 transactions · 15 stateful · 2026-09-20 04:53:02 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
2.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,372,750 · 16 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
1w02w14w18w29w310w111w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7e818a1…8259
0x34b655…2a6f
14 touches
21 conflicts
0x8d664414…3344
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x282d0473…a801
0x34b655…2a6f
10 touches
10 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
6 touches
3 conflicts
0x1785cf5f…58ba
0x34b655…2a6f
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
21 conflicts on slot 0xa7e818a1d5…208259
Audit this contract →
← previous block·next block →recent activity