← previous blocknext block →recent activity
Analyzing
Block #87,734,878
17 transactions · 15 stateful · 2026-07-14 16:22:36 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,734,878 · 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
2w08w09w112w213w314w416w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xcf5ef070…7d4f
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xff1c6931…7633
0x34b655…2a6f
4 touches
1 conflict
0x9cf61590…ad8c
0x34b655…2a6f
4 touches
1 conflict
0xa7c7dd7e…ce22
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
10 conflicts on slot 0x0dd44476b8…7fef40
Audit this contract →
← previous block·next block →recent activity