← previous blocknext block →recent activity
Analyzing
Block #87,711,378
23 transactions · 22 stateful · 2026-07-14 13:45:15 UTC
Parallelism
78/100
Blocked
23%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,711,378 · 23 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
3w06w17w010w211w313w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c7d2e4b…499b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x6e088aaa…3972
0x34b655…2a6f
4 touches
1 conflict
0x85981f95…c27b
0x34b655…2a6f
4 touches
1 conflict
0x893e54e2…2205
0x34b655…2a6f
4 touches
1 conflict
0x9f3dd8dc…802a
0x34b655…2a6f
4 touches
1 conflict
0xa1210206…7aff
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 0x9c7d2e4b54…03499b
Audit this contract →
← previous block·next block →recent activity