← previous blocknext block →recent activity
Analyzing
Block #105,845,145
34 transactions · 32 stateful · 2026-09-18 08:36:36 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.59
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,845,145 · 34 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
2w03w14w25w36w47w510w511w612w727w828w929w930w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e1fd490…d0ee
0x34b655…2a6f
14 touches
21 conflicts
0x122e2052…2bfe
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x8db32935…81a7
0x34b655…2a6f
10 touches
10 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
10 touches
10 conflicts
0x90a021f0…f922
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
8 touches
6 conflicts
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 0x5e1fd49037…13d0ee
Audit this contract →
← previous block·next block →recent activity