← previous blocknext block →recent activity
Analyzing
Block #105,605,807
36 transactions · 32 stateful · 2026-09-17 12:30:34 UTC
Parallelism
50/100
Blocked
69%
Avg conflicts / tx
2.86
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #105,605,807 · 36 txs across 18 waves · depth 18
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
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w38w49w510w611w712w813w914w1015w1118w423w1035w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
12 touches
15 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
10 touches
10 conflicts
0x4740bee7…3755
0x34b655…2a6f
10 touches
10 conflicts
0x58f3a238…24bd
0x34b655…2a6f
10 touches
10 conflicts
0x5f76b8ee…ecfe
0x34b655…2a6f
10 touches
10 conflicts
0x7006165a…df17
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
66 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity