← previous blocknext block →recent activity
Analyzing
Block #87,614,412
21 transactions · 19 stateful · 2026-07-14 02:56:51 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,614,412 · 21 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
3w05w16w27w311w312w413w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06c2cf5…61bd
0x34b655…2a6f
6 touches
3 conflicts
0x59a54ff4…d21b
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x71604178…a3a8
0x34b655…2a6f
6 touches
3 conflicts
0x71806e15…2893
0x34b655…2a6f
6 touches
3 conflicts
0x943b92d0…dfee
0x34b655…2a6f
6 touches
3 conflicts
0xb6aedce9…a483
0x34b655…2a6f
6 touches
3 conflicts
0xe8352ac7…d7a3
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0xf06c2cf5e4…3161bd
Audit this contract →
← previous block·next block →recent activity