← previous blocknext block →recent activity
Analyzing
Block #87,355,385
17 transactions · 16 stateful · 2026-07-12 22:03:44 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,355,385 · 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
2w03w15w07w08w111w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00b4a6c8…959f
0x34b655…2a6f
4 touches
1 conflict
0x07f66b29…8c35
0x34b655…2a6f
4 touches
1 conflict
0x25dc97b9…21fa
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x5b813b1d…5968
0x34b655…2a6f
4 touches
1 conflict
0x6273cfa1…f89c
0x34b655…2a6f
4 touches
1 conflict
0x636fd21a…9978
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
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 0x00b4a6c8a0…75959f
Audit this contract →
← previous block·next block →recent activity