← previous blocknext block →recent activity
Analyzing
Block #85,375,482
26 transactions · 24 stateful · 2026-07-03 17:43:27 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,375,482 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w07w19w010w111w012w115w216w321w122w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6805ef8…e22e
0x34b655…2a6f
6 touches
3 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
4 touches
1 conflict
0xb43dc900…22f2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x15a8dcd6…2c36
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x5f34fd08…aeb3
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xe6805ef89e…4fe22e
Audit this contract →
← previous block·next block →recent activity