← previous blocknext block →recent activity
Analyzing
Block #87,712,039
22 transactions · 18 stateful · 2026-07-14 13:49:40 UTC
Parallelism
73/100
Blocked
39%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,712,039 · 22 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
2w03w18w113w214w315w418w019w120w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d85c11e…9c54
0x34b655…2a6f
8 touches
6 conflicts
0xb65644e3…33ce
0x34b655…2a6f
8 touches
6 conflicts
0x42578f4c…5779
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x9170ba2e…39c8
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 0x6d85c11e6e…409c54
Audit this contract →
← previous block·next block →recent activity