← previous blocknext block →recent activity
Analyzing
Block #105,576,489
18 transactions · 14 stateful · 2026-09-17 10:02:59 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,576,489 · 18 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
1w02w04w05w18w114w215w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3a187e4…4b9b
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x9be5fcbc…11d8
0x34b655…2a6f
6 touches
3 conflicts
0x2242a1ee…5035
0x34b655…2a6f
6 touches
3 conflicts
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x5556298f…e9b0
0x34b655…2a6f
4 touches
1 conflict
0x5b0a33d1…f825
0x34b655…2a6f
4 touches
1 conflict
0x5eb187dd…b1d6
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 0xd3a187e4d0…a64b9b
Audit this contract →
← previous block·next block →recent activity