← previous blocknext block →recent activity
Analyzing
Block #87,512,668
15 transactions · 15 stateful · 2026-07-13 15:35:42 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,512,668 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w211w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05f4877e…8ca1
0x34b655…2a6f
4 touches
1 conflict
0x1274880c…3cdc
0x34b655…2a6f
4 touches
1 conflict
0x18ca6535…87c1
0x34b655…2a6f
4 touches
1 conflict
0x20e3850b…76b3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5da51ab8…1812
0x34b655…2a6f
4 touches
1 conflict
0x69a0a437…758c
0x34b655…2a6f
4 touches
1 conflict
0x6b2ba712…0214
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 0x05f4877e7e…458ca1
Audit this contract →
← previous block·next block →recent activity