← previous blocknext block →recent activity
Analyzing
Block #105,760,570
21 transactions · 21 stateful · 2026-09-18 01:29:32 UTC
Parallelism
62/100
Blocked
48%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,760,570 · 21 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
2w04w17w08w19w211w012w313w414w515w516w617w720w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5eb6a5ed…acf8
0x34b655…2a6f
12 touches
15 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
10 touches
10 conflicts
0x89472a26…7ec8
0x34b655…2a6f
8 touches
6 conflicts
0x953517cb…cdec
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x9c2fc330…0091
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x5eb6a5ed5e…f8acf8
Audit this contract →
← previous block·next block →recent activity