← previous blocknext block →recent activity
Analyzing
Block #87,621,700
20 transactions · 19 stateful · 2026-07-14 03:45:34 UTC
Parallelism
50/100
Blocked
47%
Avg conflicts / tx
1.1
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,621,700 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w310w412w514w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc514314c…1aa4
0x34b655…2a6f
8 touches
6 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x69ce640b…884a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9d9b4da9…ecf3
0x34b655…2a6f
4 touches
1 conflict
0xc9377f93…3739
0x34b655…2a6f
4 touches
1 conflict
0xcd26ecec…e406
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 0xc514314ca6…fa1aa4
Audit this contract →
← previous block·next block →recent activity