← previous blocknext block →recent activity
Analyzing
Block #87,504,006
15 transactions · 14 stateful · 2026-07-13 14:37:41 UTC
Parallelism
53/100
Blocked
43%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,504,006 · 15 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
2w03w14w26w37w49w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0xc3688185…9b36
0x34b655…2a6f
6 touches
3 conflicts
0xe021dbc8…d27b
0x34b655…2a6f
4 touches
1 conflict
0x9265e686…7bb5
0x34b655…2a6f
4 touches
1 conflict
0x9265e686…7bb6
0x34b655…2a6f
4 touches
1 conflict
0xbe4a325a…ac1e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc90601f4…1588
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 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity