← previous blocknext block →recent activity
Analyzing
Block #87,783,528
20 transactions · 18 stateful · 2026-07-14 21:48:04 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,783,528 · 20 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
1w02w16w09w011w113w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd38ec0c6…76d7
0x34b655…2a6f
4 touches
1 conflict
0xdbdcb25c…d6b6
0x34b655…2a6f
4 touches
1 conflict
0xdc204ea3…f1a3
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x33d170e2…2c61
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 0xd38ec0c6eb…4776d7
Audit this contract →
← previous block·next block →recent activity