← previous blocknext block →recent activity
Analyzing
Block #105,403,045
35 transactions · 30 stateful · 2026-09-16 19:30:05 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
1.31
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,403,045 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w07w112w213w315w216w317w418w519w621w128w429w532w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x65084079…ae48
0x34b655…2a6f
4 touches
1 conflict
0x7746704d…9928
0x34b655…2a6f
4 touches
1 conflict
0x8726b27c…9a04
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity