← previous blocknext block →recent activity
Analyzing
Block #106,370,046
24 transactions · 23 stateful · 2026-09-20 04:39:25 UTC
Parallelism
63/100
Blocked
52%
Avg conflicts / tx
2.21
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,370,046 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w18w29w010w115w317w419w520w621w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89eaf36a…4e48
0x34b655…2a6f
16 touches
28 conflicts
0x2686eb58…7c02
0x34b655…2a6f
14 touches
21 conflicts
0xf879fb7c…6785
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xdac9c1bc…c189
0x34b655…2a6f
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0xdd77da90…6df4
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
28 conflicts on slot 0x89eaf36ae4…6e4e48
Audit this contract →
← previous block·next block →recent activity