← previous blocknext block →recent activity
Analyzing
Block #87,589,412
14 transactions · 11 stateful · 2026-07-14 00:09:40 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,589,412 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5831d96b…44a7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd2261656…c9d6
0x34b655…2a6f
4 touches
1 conflict
0xd2261656…c9d7
0x34b655…2a6f
4 touches
1 conflict
0xdc26de8c…939c
0x34b655…2a6f
4 touches
1 conflict
0x18904470…0ef9
0x34b655…2a6f
4 touches
1 conflict
0x69ce640b…884a
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
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 0x5831d96b29…4b44a7
Audit this contract →
← previous block·next block →recent activity