← previous blocknext block →recent activity
Analyzing
Block #87,455,533
13 transactions · 11 stateful · 2026-07-13 09:13:30 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,455,533 · 13 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
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x375e887b…a361
0x34b655…2a6f
6 touches
3 conflicts
0x71cd2af8…dbd4
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x9b02ba92…7100
0x34b655…2a6f
6 touches
3 conflicts
0xb3e53c5e…b99c
0x34b655…2a6f
6 touches
3 conflicts
0x4b3333e9…2fdd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x73ab4c24…1861
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
3 conflicts on slot 0x375e887ba8…b7a361
Audit this contract →
← previous block·next block →recent activity