← previous blocknext block →recent activity
Analyzing
Block #87,718,512
14 transactions · 11 stateful · 2026-07-14 14:33:08 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,718,512 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1eed1f5…0770
0x34b655…2a6f
4 touches
1 conflict
0x0ea06e29…aa72
0x34b655…2a6f
4 touches
1 conflict
0x1526b11f…8b21
0x34b655…2a6f
4 touches
1 conflict
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x7cb1d883…dc23
0x34b655…2a6f
4 touches
1 conflict
0xa558e115…fc88
0x34b655…2a6f
4 touches
1 conflict
0xa6c9a33e…d839
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 0xb1eed1f584…e90770
Audit this contract →
← previous block·next block →recent activity