← previous blocknext block →recent activity
Analyzing
Block #105,672,415
13 transactions · 12 stateful · 2026-09-17 18:05:53 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,672,415 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5f5f775…010b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x51f30aee…bfbf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x346bf59b…8fb6
0x34b655…2a6f
2 touches
0 conflicts
0x34ba96d4…b1f7
0x34b655…2a6f
2 touches
0 conflicts
0x5c44de00…1a96
0x34b655…2a6f
2 touches
0 conflicts
0x5ddc4a77…765e
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xb5f5f77567…50010b
Audit this contract →
← previous block·next block →recent activity