← previous blocknext block →recent activity
Analyzing
Block #86,673,664
17 transactions · 12 stateful · 2026-07-09 18:07:01 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,673,664 · 17 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
6w07w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e10b712…1fc2
0x34b655…2a6f
4 touches
1 conflict
0xa248a5dd…4a69
0x34b655…2a6f
4 touches
1 conflict
0xad862891…5d02
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x145b9bbf…e50e
0x34b655…2a6f
4 touches
1 conflict
0x145b9bbf…e50f
0x34b655…2a6f
4 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
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
1 conflict on slot 0x9e10b71208…5e1fc2
Audit this contract →
← previous block·next block →recent activity