← previous blocknext block →recent activity
Analyzing
Block #105,550,254
17 transactions · 17 stateful · 2026-09-17 07:50:57 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,550,254 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w010w011w112w213w315w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebe581d8…2696
0x34b655…2a6f
8 touches
6 conflicts
0xb20408ae…a2a5
0x34b655…2a6f
8 touches
6 conflicts
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0x758a0dd5…0f46
0x34b655…2a6f
6 touches
3 conflicts
0xf26a1736…a588
0x34b655…2a6f
4 touches
1 conflict
0x0c7103bd…4f89
0x34b655…2a6f
4 touches
1 conflict
0x13d4d00c…f4e6
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
6 conflicts on slot 0xebe581d8e8…f12696
Audit this contract →
← previous block·next block →recent activity