← previous blocknext block →recent activity
Analyzing
Block #87,715,567
25 transactions · 25 stateful · 2026-07-14 14:13:21 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,715,567 · 25 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
1w02w13w07w18w213w114w217w118w019w221w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2385516f…eca5
0x34b655…2a6f
6 touches
3 conflicts
0xc8536f01…eb88
0x34b655…2a6f
6 touches
3 conflicts
0x7fa1794c…3323
0x34b655…2a6f
6 touches
3 conflicts
0x2e5a688b…41b9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5c3cb0f1…a9fa
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
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
3 conflicts on slot 0x2385516f6a…9aeca5
Audit this contract →
← previous block·next block →recent activity