← previous blocknext block →recent activity
Analyzing
Block #87,738,517
18 transactions · 16 stateful · 2026-07-14 16:46:57 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,738,517 · 18 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
4w05w16w27w39w010w111w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a2de05d…3e6b
0x34b655…2a6f
10 touches
10 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
8 touches
6 conflicts
0x58620f29…db5a
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
8 touches
6 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
8 touches
6 conflicts
0xa80038e1…4b49
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
10 conflicts on slot 0x9a2de05d75…453e6b
Audit this contract →
← previous block·next block →recent activity