← previous blocknext block →recent activity
Analyzing
Block #85,136,283
19 transactions · 16 stateful · 2026-07-02 15:10:07 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,136,283 · 19 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
1w02w03w010w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2697123c…8526
0x34b655…2a6f
6 touches
3 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x06d80e11…d107
0x34b655…2a6f
4 touches
1 conflict
0x0db8e93a…7dd1
0x34b655…2a6f
4 touches
1 conflict
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0x4fefe22e…64d4
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 0x2697123ce4…5e8526
Audit this contract →
← previous block·next block →recent activity