← previous blocknext block →recent activity
Analyzing
Block #87,627,625
16 transactions · 12 stateful · 2026-07-14 04:25:14 UTC
Parallelism
63/100
Blocked
42%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,627,625 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef1cbbb7…8cc8
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xb91a6f59…722c
0x34b655…2a6f
6 touches
3 conflicts
0x0d9abeda…de75
0x34b655…2a6f
4 touches
1 conflict
0x0dcb313d…7073
0x34b655…2a6f
4 touches
1 conflict
0x117cb8ea…a1dc
0x34b655…2a6f
4 touches
1 conflict
0x11e1426c…0d03
0x34b655…2a6f
4 touches
1 conflict
0x159aac52…c583
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
6 conflicts on slot 0xef1cbbb7ac…328cc8
Audit this contract →
← previous block·next block →recent activity