← previous blocknext block →recent activity
Analyzing
Block #87,307,311
17 transactions · 16 stateful · 2026-07-12 16:42:16 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,307,311 · 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
3w04w17w08w09w112w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb564c7f…72f9
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x13c93515…6c61
0x34b655…2a6f
4 touches
1 conflict
0x167f697f…7f61
0x34b655…2a6f
4 touches
1 conflict
0x167f697f…7f62
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x351fa26b…2018
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 0xdb564c7f1e…2172f9
Audit this contract →
← previous block·next block →recent activity