← previous blocknext block →recent activity
Analyzing
Block #85,576,329
13 transactions · 8 stateful · 2026-07-04 16:00:38 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,576,329 · 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
1w02w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10c9dff3…8ea4
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x216c7474…02df
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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 0x10c9dff371…a88ea4
Audit this contract →
← previous block·next block →recent activity