← previous blocknext block →recent activity
Analyzing
Block #105,606,501
28 transactions · 25 stateful · 2026-09-17 12:34:03 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,606,501 · 28 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
1w02w13w24w05w06w17w08w116w217w220w321w322w424w327w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae4628cb…9d8d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x93afca4c…b47b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xae4628cb42…579d8d
Audit this contract →
← previous block·next block →recent activity