← previous blocknext block →recent activity
Analyzing
Block #87,626,536
29 transactions · 21 stateful · 2026-07-14 04:17:56 UTC
Parallelism
86/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,626,536 · 29 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
1w04w06w07w18w09w110w211w317w018w119w121w227w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0xac61d3a4…7da8
0x34b655…2a6f
6 touches
3 conflicts
0xc514314c…1aa4
0x34b655…2a6f
6 touches
3 conflicts
0x952e910f…0001
0x34b655…2a6f
4 touches
1 conflict
0xc6ed530e…fa7d
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity