← previous blocknext block →recent activity
Analyzing
Block #105,845,330
19 transactions · 17 stateful · 2026-09-18 08:37:33 UTC
Parallelism
63/100
Blocked
41%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,845,330 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w111w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x661e648a…2aa7
0x34b655…2a6f
14 touches
21 conflicts
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
8 touches
6 conflicts
0x2dee67c5…5566
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
21 conflicts on slot 0xfd7f5b557f…f74994
Audit this contract →
← previous block·next block →recent activity