← previous blocknext block →recent activity
Analyzing
Block #87,755,313
16 transactions · 15 stateful · 2026-07-14 18:39:18 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,755,313 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w17w18w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0x819b5176…86cf
0x34b655…2a6f
8 touches
6 conflicts
0x33da0dfa…bac6
0x34b655…2a6f
8 touches
6 conflicts
0x3f7d8a09…362c
0x34b655…2a6f
6 touches
3 conflicts
0x51f60b9d…653f
0x34b655…2a6f
6 touches
3 conflicts
0xfcea0c54…587f
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x3f1a31b5…9888
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
6 conflicts on slot 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity