← previous blocknext block →recent activity
Analyzing
Block #87,595,135
21 transactions · 18 stateful · 2026-07-14 00:47:57 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,595,135 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w39w010w011w412w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x7527802e…2ba9
0x34b655…2a6f
10 touches
10 conflicts
0xd7fe05cd…207e
0x34b655…2a6f
8 touches
6 conflicts
0xed03f7f5…68b3
0x34b655…2a6f
8 touches
6 conflicts
0x17c70f19…23a7
0x34b655…2a6f
4 touches
1 conflict
0x18904470…0ef9
0x34b655…2a6f
4 touches
1 conflict
0x27bfe98b…2053
0x34b655…2a6f
4 touches
1 conflict
0x2aaaf16f…3fe4
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity