← previous blocknext block →recent activity
Analyzing
Block #87,724,924
17 transactions · 16 stateful · 2026-07-14 15:16:01 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,724,924 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w012w113w214w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f35c56f…046b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9cea6ca2…570e
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc4de6652…13f4
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
3 conflicts on slot 0x2f35c56f7b…bd046b
Audit this contract →
← previous block·next block →recent activity