← previous blocknext block →recent activity
Analyzing
Block #105,683,729
21 transactions · 19 stateful · 2026-09-17 19:02:49 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,683,729 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w07w113w216w217w318w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a9ce11b…a0d1
0x34b655…2a6f
10 touches
10 conflicts
0xb6e328b2…5194
0x34b655…2a6f
8 touches
6 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x26bb6db7…f860
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x3dae5ee1…721b
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
10 conflicts on slot 0x6a9ce11b1a…63a0d1
Audit this contract →
← previous block·next block →recent activity