← previous blocknext block →recent activity
Analyzing
Block #87,417,995
16 transactions · 14 stateful · 2026-07-13 05:02:34 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,417,995 · 16 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
1w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x58d0a23c…5d3a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x01c969a3…227b
0x34b655…2a6f
2 touches
0 conflicts
0x02f0ef4a…7144
0x34b655…2a6f
2 touches
0 conflicts
0x03e04666…3ed5
0x34b655…2a6f
2 touches
0 conflicts
0x06040b44…e244
0x34b655…2a6f
2 touches
0 conflicts
0x09c544ee…318d
0x34b655…2a6f
2 touches
0 conflicts
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity