← previous blocknext block →recent activity
Analyzing
Block #105,583,917
13 transactions · 12 stateful · 2026-09-17 10:40:22 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,583,917 · 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
5w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ecb9366…f4f2
0x34b655…2a6f
4 touches
1 conflict
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x0cc532d4…d712
0x34b655…2a6f
2 touches
0 conflicts
0x0e7cd7c8…e090
0x34b655…2a6f
2 touches
0 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x26c599c1…706c
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 0x3ecb93668a…3df4f2
Audit this contract →
← previous block·next block →recent activity