← previous blocknext block →recent activity
Analyzing
Block #87,418,087
18 transactions · 17 stateful · 2026-07-13 05:03:11 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,418,087 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w211w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca32a09…4e48
0x34b655…2a6f
10 touches
10 conflicts
0xc3227661…a8b3
0x34b655…2a6f
6 touches
3 conflicts
0x7c63ea28…e8af
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xb7e4c78a…f3f6
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x621d768f…a8cb
0x34b655…2a6f
4 touches
1 conflict
0x67bfbc55…7b2f
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
10 conflicts on slot 0x6ca32a096a…2c4e48
Audit this contract →
← previous block·next block →recent activity