← previous blocknext block →recent activity
Analyzing
Block #87,304,381
16 transactions · 15 stateful · 2026-07-12 16:22:41 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,304,381 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w38w09w310w411w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d4584df…ffed
0x34b655…2a6f
8 touches
6 conflicts
0xa4e5e0c2…6e04
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x66d961e5…1d87
0x34b655…2a6f
4 touches
1 conflict
0x80c280c3…6bba
0x34b655…2a6f
4 touches
1 conflict
0x84838d52…47e8
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 0x3d4584dfb2…87ffed
Audit this contract →
← previous block·next block →recent activity