← previous blocknext block →recent activity
Analyzing
Block #107,441,403
20 transactions · 18 stateful · 2026-09-23 22:33:15 UTC
Parallelism
80/100
Blocked
28%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,441,403 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w111w112w213w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fa4ba1b…750c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2bb8f8c9…2610
0x34b655…2a6f
6 touches
3 conflicts
0x2abae95e…7d60
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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
6 conflicts on slot 0x8fa4ba1b4e…e5750c
Audit this contract →
← previous block·next block →recent activity