← previous blocknext block →recent activity
Analyzing
Block #87,419,571
22 transactions · 21 stateful · 2026-07-13 05:13:05 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,419,571 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w18w29w312w416w518w119w020w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab360ba6…efc4
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0xd330c0c5…6f64
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x88413c1a…7783
0x34b655…2a6f
4 touches
1 conflict
0xa190f35e…7057
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
10 conflicts on slot 0xab360ba6a4…ffefc4
Audit this contract →
← previous block·next block →recent activity