← previous blocknext block →recent activity
Analyzing
Block #87,257,080
17 transactions · 15 stateful · 2026-07-12 11:06:28 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.41
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,257,080 · 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
1w02w15w06w19w010w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf85fbefc…6825
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x52dbed73…7fdb
0x34b655…2a6f
4 touches
1 conflict
0x7139bf32…c881
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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 0xf85fbefc8f…bd6825
Audit this contract →
← previous block·next block →recent activity