← previous blocknext block →recent activity
Analyzing
Block #85,140,140
15 transactions · 15 stateful · 2026-07-02 15:35:52 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,140,140 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w28w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x634daab4…dd5e
0x34b655…2a6f
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x07f80636…53da
0x34b655…2a6f
4 touches
1 conflict
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x61c4285d…4d90
0x34b655…2a6f
4 touches
1 conflict
0x7af4b011…96f5
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
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
3 conflicts on slot 0x634daab4a2…5edd5e
Audit this contract →
← previous block·next block →recent activity