← previous blocknext block →recent activity
Analyzing
Block #105,573,861
20 transactions · 20 stateful · 2026-09-17 09:49:45 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,573,861 · 20 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
3w04w06w19w010w112w213w014w315w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef5959a3…2a2f
0x34b655…2a6f
10 touches
10 conflicts
0x67faf0c9…2ddb
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xf346808d…6ad4
0x34b655…2a6f
6 touches
3 conflicts
0x6771eae2…7014
0x34b655…2a6f
6 touches
3 conflicts
0x947bb79d…6458
0x34b655…2a6f
6 touches
3 conflicts
0x8968fc32…20e3
0x34b655…2a6f
4 touches
1 conflict
0x91bb1de1…d675
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
10 conflicts on slot 0xef5959a35a…d32a2f
Audit this contract →
← previous block·next block →recent activity