← previous blocknext block →recent activity
Analyzing
Block #87,504,516
19 transactions · 19 stateful · 2026-07-13 14:41:09 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,504,516 · 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
2w03w15w06w07w18w213w315w418w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x2a9f9737…d07d
0x34b655…2a6f
4 touches
1 conflict
0x2b593776…60ed
0x34b655…2a6f
4 touches
1 conflict
0x300d6f8b…c4fe
0x34b655…2a6f
4 touches
1 conflict
0x3d4c0233…20a5
0x34b655…2a6f
4 touches
1 conflict
0x41e2ea73…ddf8
0x34b655…2a6f
4 touches
1 conflict
0x4eadeb78…3f1f
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity