← previous blocknext block →recent activity
Analyzing
Block #87,496,529
30 transactions · 19 stateful · 2026-07-13 13:47:39 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,496,529 · 30 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
1w03w19w010w011w112w013w117w018w119w220w324w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2a49f3bf…713b
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7103aaf4…ddc5
0x34b655…2a6f
4 touches
1 conflict
0x792bcf31…6a9d
0x34b655…2a6f
4 touches
1 conflict
0x7df41046…7f1a
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 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity