← previous blocknext block →recent activity
Analyzing
Block #87,621,842
19 transactions · 16 stateful · 2026-07-14 03:46:31 UTC
Parallelism
74/100
Blocked
25%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,621,842 · 19 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
5w07w18w210w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x640530ff…86bc
0x34b655…2a6f
8 touches
6 conflicts
0xf2f40f08…5cdb
0x34b655…2a6f
6 touches
3 conflicts
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x944bfd2a…49f7
0x34b655…2a6f
6 touches
3 conflicts
0x05dabb1a…f91e
0x34b655…2a6f
6 touches
3 conflicts
0x51f60b9d…653f
0x34b655…2a6f
4 touches
1 conflict
0x59c89f2b…2f10
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 0x640530ff6c…0186bc
Audit this contract →
← previous block·next block →recent activity