← previous blocknext block →recent activity
Analyzing
Block #87,497,628
36 transactions · 28 stateful · 2026-07-13 13:55:01 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,497,628 · 36 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
1w04w05w16w07w18w09w116w117w218w321w124w125w232w333w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x24d68cf2…09b7
0x34b655…2a6f
6 touches
3 conflicts
0xd5dbfacf…c5ec
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4e1ce17e…98a7
0x34b655…2a6f
6 touches
3 conflicts
0x53111a4d…34f6
0x34b655…2a6f
6 touches
3 conflicts
0xa241f0f0…ca94
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
3 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity