← previous blocknext block →recent activity
Analyzing
Block #85,352,131
16 transactions · 14 stateful · 2026-07-03 15:07:49 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,352,131 · 16 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
2w03w15w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x2d8487d0…24c6
0x34b655…2a6f
3 touches
1 conflict
0xe87e2f8a…32ab
0x34b655…2a6f
3 touches
1 conflict
0x00bac013…a28c
0x91b81b…6d56
2 touches
0 conflicts
0x9560013d…8caf
0x91b81b…6d56
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 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity