← previous blocknext block →recent activity
Analyzing
Block #87,135,560
14 transactions · 12 stateful · 2026-07-11 21:33:07 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,135,560 · 14 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
1w02w15w07w19w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdde7eb4…ab4a
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0ea92501…8fe3
0x34b655…2a6f
4 touches
1 conflict
0x1e166a45…98a7
0x34b655…2a6f
4 touches
1 conflict
0x791af26d…abf6
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0xfdde7eb400…69ab4a
Audit this contract →
← previous block·next block →recent activity