← previous blocknext block →recent activity
Analyzing
Block #105,619,701
17 transactions · 16 stateful · 2026-09-17 13:40:30 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,619,701 · 17 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
1w03w14w25w06w17w28w315w016w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x08d53462…97ef
0x34ae4d…3fc5
4 touches
1 conflict
0x5a409e7f…09b6
0x34ae4d…3fc5
4 touches
1 conflict
0x7a12283f…b18a
0x34ae4d…3fc5
4 touches
1 conflict
0x915c095e…c1e5
0x34ae4d…3fc5
4 touches
1 conflict
0xcfe06a18…b5b5
0x34ae4d…3fc5
4 touches
1 conflict
0xd8fd2add…50fc
0x34ae4d…3fc5
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity