← previous blocknext block →recent activity
Analyzing
Block #87,593,429
16 transactions · 13 stateful · 2026-07-14 00:36:32 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,593,429 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x167de262…f61f
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x34d95d94…3a16
0x34b655…2a6f
8 touches
6 conflicts
0xd11dcf4e…518f
0x34b655…2a6f
8 touches
6 conflicts
0xd19c9d38…b459
0x34b655…2a6f
8 touches
6 conflicts
0x9dc4d309…2302
0x34b655…2a6f
6 touches
3 conflicts
0x2fade833…5de4
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 0x167de262c8…3ef61f
Audit this contract →
← previous block·next block →recent activity