← previous blocknext block →recent activity
Analyzing
Block #87,613,768
17 transactions · 14 stateful · 2026-07-14 02:52:33 UTC
Parallelism
76/100
Blocked
21%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,613,768 · 17 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
3w06w07w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xffcb5f20…df5a
0x34b655…2a6f
6 touches
3 conflicts
0x4688dd30…ef52
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x5e17e5be…d212
0x34b655…2a6f
4 touches
1 conflict
0x6cd5cae5…1031
0x34b655…2a6f
4 touches
1 conflict
0x76c4d722…afa9
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity