← previous blocknext block →recent activity
Analyzing
Block #106,223,746
29 transactions · 28 stateful · 2026-09-19 16:23:08 UTC
Parallelism
59/100
Blocked
57%
Avg conflicts / tx
2.1
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,223,746 · 29 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w09w010w111w212w313w414w515w616w719w121w822w223w324w925w1026w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x7e5200db…b46f
0x34b655…2a6f
16 touches
28 conflicts
0x6d529d15…1f87
0x34b655…2a6f
16 touches
28 conflicts
0x5ef1ef7b…f42e
0x34b655…2a6f
15 touches
28 conflicts
0x1c4e2024…526c
0x34b655…2a6f
10 touches
10 conflicts
0x206f4379…e08a
0x34b655…2a6f
8 touches
6 conflicts
0xcf26f281…7b9c
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity