← previous blocknext block →recent activity
Analyzing
Block #87,738,771
17 transactions · 16 stateful · 2026-07-14 16:48:39 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,738,771 · 17 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
2w03w14w25w36w47w515w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
8 touches
6 conflicts
0x58620f29…db5a
0x34b655…2a6f
8 touches
6 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x9a2de05d…3e6b
0x34b655…2a6f
8 touches
6 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
8 touches
6 conflicts
0x58b1c0e7…8f68
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity