← previous blocknext block →recent activity
Analyzing
Block #105,601,369
20 transactions · 20 stateful · 2026-09-17 12:08:12 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,601,369 · 20 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
1w02w13w24w35w46w59w011w112w015w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf48fa71e…bb52
0x34b655…2a6f
11 touches
15 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
8 touches
6 conflicts
0x3965cb56…5369
0x34b655…2a6f
8 touches
6 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
8 touches
6 conflicts
0x41c48b64…f968
0x34b655…2a6f
8 touches
6 conflicts
0x83e91e67…3751
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xf48fa71eee…43bb52
Audit this contract →
← previous block·next block →recent activity