← previous blocknext block →recent activity
Analyzing
Block #85,536,490
13 transactions · 12 stateful · 2026-07-04 11:35:20 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,536,490 · 13 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
1w06w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x7f5178e1…41b4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdfd1d8c8…18e1
0x065c9d…c394
3 touches
1 conflict
0x00d547f3…be43
0x065c9d…c394
3 touches
1 conflict
0x138ef6d6…0bf2
0x065c9d…c394
3 touches
1 conflict
0x754bcf67…a750
0x065c9d…c394
3 touches
1 conflict
0x89999c15…fdac
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 0x664bf99ec8…ec0a8c
Audit this contract →
← previous block·next block →recent activity