← previous blocknext block →recent activity
Analyzing
Block #85,173,874
12 transactions · 11 stateful · 2026-07-02 19:20:25 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,173,874 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa5b76b…60db
0x34b655…2a6f
4 touches
1 conflict
0x2b111712…0e59
0x34b655…2a6f
4 touches
1 conflict
0x14d04bf5…6c57
0x34b655…2a6f
4 touches
1 conflict
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x63491cb0…5c0b
0x34b655…2a6f
4 touches
1 conflict
0x8d4c0bb9…ccd3
0x34b655…2a6f
4 touches
1 conflict
0xb9bc1dfc…6bfb
0x34b655…2a6f
4 touches
1 conflict
0x105a56d2…55c6
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x0aa5b76bf8…b060db
Audit this contract →
← previous block·next block →recent activity