← previous blocknext block →recent activity
Analyzing
Block #87,488,231
14 transactions · 13 stateful · 2026-07-13 12:52:07 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
1.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,488,231 · 14 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
2w03w14w25w36w48w59w010w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f7468d8…3cbc
0x34b655…2a6f
12 touches
15 conflicts
0x57c8db9d…3979
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x4ca81ae8…01d4
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x3f7468d8c0…f73cbc
Audit this contract →
← previous block·next block →recent activity