← previous blocknext block →recent activity
Analyzing
Block #85,190,105
23 transactions · 19 stateful · 2026-07-02 21:08:33 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,190,105 · 23 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
1w05w16w07w18w210w011w112w213w314w019w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
6 touches
3 conflicts
0x1ee44d08…7262
0x34b655…2a6f
6 touches
3 conflicts
0x301e1c77…9e30
0x34b655…2a6f
6 touches
3 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
6 touches
3 conflicts
0x5ad3280d…16bb
0x34b655…2a6f
6 touches
3 conflicts
0x6167486f…db40
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity