← previous blocknext block →recent activity
Analyzing
Block #87,520,079
19 transactions · 17 stateful · 2026-07-13 16:25:29 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,520,079 · 19 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
1w02w15w06w17w18w29w310w114w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x034d14da…9f5f
0x34b655…2a6f
4 touches
1 conflict
0x092832cd…7b28
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x3a7fb5b5…f0e5
0x34b655…2a6f
4 touches
1 conflict
0x469e824a…d814
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x55eef346…d185
0x34b655…2a6f
4 touches
1 conflict
0x5a6864fe…2890
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 0x034d14dad5…359f5f
Audit this contract →
← previous block·next block →recent activity