← previous blocknext block →recent activity
Analyzing
Block #87,760,542
13 transactions · 11 stateful · 2026-07-14 19:14:15 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,760,542 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w09w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x199944d5…ab9f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x50ff67ff…7fb8
0x34b655…2a6f
4 touches
1 conflict
0x50ff67ff…7fb9
0x34b655…2a6f
4 touches
1 conflict
0x601d83d0…a856
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x8fcb5e9e…294e
0x34b655…2a6f
4 touches
1 conflict
0x9666da3b…0f0e
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
1 conflict on slot 0x199944d5b2…25ab9f
Audit this contract →
← previous block·next block →recent activity