← previous blocknext block →recent activity
Analyzing
Block #87,078,830
16 transactions · 15 stateful · 2026-07-11 15:14:06 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,078,830 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w113w015w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x9b9168c0…f516
0x34b655…2a6f
8 touches
6 conflicts
0xc147d6ed…1f08
0x34b655…2a6f
6 touches
3 conflicts
0x103f3294…1abb
0x34b655…2a6f
4 touches
1 conflict
0x103f3294…1abc
0x34b655…2a6f
4 touches
1 conflict
0x169daa40…3f75
0x34b655…2a6f
4 touches
1 conflict
0x1af19f5c…aee2
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity