← previous blocknext block →recent activity
Analyzing
Block #87,737,591
18 transactions · 16 stateful · 2026-07-14 16:40:45 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,737,591 · 18 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
3w05w06w17w28w113w314w215w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d4c0bb9…ccd3
0x34b655…2a6f
8 touches
6 conflicts
0x58620f29…db5a
0x34b655…2a6f
6 touches
3 conflicts
0x0363d65e…06d2
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x9001f549…089d
0x34b655…2a6f
4 touches
1 conflict
0x4e0c0a07…c508
0x34b655…2a6f
4 touches
1 conflict
0x5f72d58f…c445
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 0x8d4c0bb98b…d4ccd3
Audit this contract →
← previous block·next block →recent activity