← previous blocknext block →recent activity
Analyzing
Block #87,578,509
23 transactions · 21 stateful · 2026-07-13 22:56:45 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,578,509 · 23 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
1w02w15w06w110w012w117w218w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0x6cd5cae5…1031
0x34b655…2a6f
6 touches
3 conflicts
0x978c66ea…b1ef
0x34b655…2a6f
6 touches
3 conflicts
0x59a54ff4…d21b
0x34b655…2a6f
6 touches
3 conflicts
0x11e1426c…0d03
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
0x4f1e16d4…4833
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity