← previous blocknext block →recent activity
Analyzing
Block #87,615,253
16 transactions · 14 stateful · 2026-07-14 03:02:29 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,615,253 · 16 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
1w02w13w04w17w28w39w110w311w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe197e523…ef9c
0x34b655…2a6f
6 touches
3 conflicts
0x006b549f…13a3
0x34b655…2a6f
4 touches
1 conflict
0x06eb4e3a…849c
0x34b655…2a6f
4 touches
1 conflict
0x07f69062…03ec
0x34b655…2a6f
4 touches
1 conflict
0x1ee4a6d2…6389
0x34b655…2a6f
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
4 touches
1 conflict
0x354a9394…a311
0x34b655…2a6f
4 touches
1 conflict
0x3c8c4674…a567
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 0xe197e52366…87ef9c
Audit this contract →
← previous block·next block →recent activity