← previous blocknext block →recent activity
Analyzing
Block #105,850,409
32 transactions · 30 stateful · 2026-09-18 09:03:07 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,850,409 · 32 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
1w02w03w04w05w06w18w19w010w112w116w117w220w222w224w225w326w127w230w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55192654…91fe
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6324ccc9…14fd
0x34b655…2a6f
4 touches
1 conflict
0x63feb930…1c80
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
6 conflicts on slot 0x551926541c…2e91fe
Audit this contract →
← previous block·next block →recent activity