← previous blocknext block →recent activity
Analyzing
Block #87,706,202
30 transactions · 25 stateful · 2026-07-14 13:10:37 UTC
Parallelism
90/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,706,202 · 30 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w18w09w113w014w017w119w220w122w223w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
0x43fab434…896f
0xa6afd3…d132
4 touches
1 conflict
0x7eb441f4…271a
0xa6afd3…d132
4 touches
1 conflict
0x8fa9bc45…e08f
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: 0xc1ff9fef…f4b0fc
1 conflict on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity