← previous blocknext block →recent activity
Analyzing
Block #106,040,554
20 transactions · 19 stateful · 2026-09-19 01:01:09 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,040,554 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w27w08w115w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfac38cc8…fb9d
0x34b655…2a6f
6 touches
3 conflicts
0xf57a1b3e…7611
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb88f1ce7…4fe9
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x53e50026…6d8c
0x34ae4d…3fc5
2 touches
0 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
3 conflicts on slot 0xfac38cc8b7…a4fb9d
Audit this contract →
← previous block·next block →recent activity