← previous blocknext block →recent activity
Analyzing
Block #106,163,680
38 transactions · 38 stateful · 2026-09-19 11:20:48 UTC
Parallelism
66/100
Blocked
74%
Avg conflicts / tx
2.74
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,163,680 · 38 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w27w29w211w115w316w421w224w525w626w727w828w129w930w1031w1132w1236w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9430e759…86df
0x34b655…2a6f
18 touches
36 conflicts
0x0e3c14ef…5edf
0x34b655…2a6f
16 touches
28 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
10 touches
10 conflicts
0x57c59b92…6b86
0x34b655…2a6f
8 touches
6 conflicts
0x61037d3e…1885
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
36 conflicts on slot 0x9430e759ab…3f86df
Audit this contract →
← previous block·next block →recent activity