← previous blocknext block →recent activity
Analyzing
Block #105,932,757
19 transactions · 19 stateful · 2026-09-18 15:58:28 UTC
Parallelism
63/100
Blocked
63%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,932,757 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w310w111w312w213w414w515w617w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb11940a…519b
0x34b655…2a6f
10 touches
10 conflicts
0x95152422…d9c3
0x34b655…2a6f
8 touches
6 conflicts
0x56df48c8…9292
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x3a429191…9cda
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xdb11940a1f…24519b
Audit this contract →
← previous block·next block →recent activity