← previous blocknext block →recent activity
Analyzing
Block #106,389,552
37 transactions · 36 stateful · 2026-09-20 06:17:36 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
1.49
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,389,552 · 37 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w110w112w218w320w221w422w523w624w725w726w827w928w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3169b10…f337
0x34b655…2a6f
14 touches
21 conflicts
0xfaee4f79…d6ee
0x34b655…2a6f
12 touches
15 conflicts
0xba33378a…f1df
0x34b655…2a6f
12 touches
15 conflicts
0xc8cb0701…3926
0x34b655…2a6f
10 touches
10 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 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 0xa3169b1014…85f337
Audit this contract →
← previous block·next block →recent activity