← previous blocknext block →recent activity
Analyzing
Block #105,931,328
29 transactions · 26 stateful · 2026-09-18 15:51:16 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,931,328 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w09w016w217w318w122w524w425w528w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a429191…9cda
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7e43e39e…1449
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x972da85f…50ab
0x1b6862…e19c
8 touches
6 conflicts
0xd4fb3441…c092
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
10 conflicts on slot 0x3a42919159…6b9cda
Audit this contract →
← previous block·next block →recent activity