← previous blocknext block →recent activity
Analyzing
Block #87,593,141
21 transactions · 20 stateful · 2026-07-14 00:34:37 UTC
Parallelism
90/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,593,141 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w012w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89a63bb6…c2b5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01c969a3…227b
0x34b655…2a6f
2 touches
0 conflicts
0x05ae4d3e…3c79
0x34b655…2a6f
2 touches
0 conflicts
0x0a5dbc1e…74cc
0x34b655…2a6f
2 touches
0 conflicts
0x12a92ce8…db54
0x34b655…2a6f
2 touches
0 conflicts
0x176771f9…c1a4
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x89a63bb6e5…dfc2b5
Audit this contract →
← previous block·next block →recent activity