← previous blocknext block →recent activity
Analyzing
Block #105,850,617
25 transactions · 23 stateful · 2026-09-18 09:04:10 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
0.92
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,850,617 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w48w19w010w511w519w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
12 touches
15 conflicts
0x51f05f20…36a4
0x34b655…2a6f
8 touches
6 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
6 touches
3 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4e0a9e70…bdb7
0x34b655…2a6f
4 touches
1 conflict
0x63feb930…1c80
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
15 conflicts on slot 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity