← previous blocknext block →recent activity
Analyzing
Block #87,621,428
18 transactions · 15 stateful · 2026-07-14 03:43:45 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,621,428 · 18 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
1w03w04w15w28w010w313w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f4727d…cdb7
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x5bd818fc…4f86
0x34b655…2a6f
4 touches
1 conflict
0x82f08cb8…4d94
0x34b655…2a6f
4 touches
1 conflict
0x82f08cb8…4d95
0x34b655…2a6f
4 touches
1 conflict
0x861788b7…8b1e
0x34b655…2a6f
4 touches
1 conflict
0x875164c2…f8a2
0x34b655…2a6f
4 touches
1 conflict
0x9407f89d…82ff
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 0xf2f4727df6…a5cdb7
Audit this contract →
← previous block·next block →recent activity