← previous blocknext block →recent activity
Analyzing
Block #87,611,028
30 transactions · 24 stateful · 2026-07-14 02:34:14 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,611,028 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w09w010w111w212w313w417w319w521w223w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x767799cd…f423
0xc8689a…ee79
4 touches
1 conflict
0xa2e89145…7dfa
0x34b655…2a6f
4 touches
1 conflict
0xcfdb3285…de33
0x34b655…2a6f
4 touches
1 conflict
0xda3eb3c3…9d60
0x34b655…2a6f
4 touches
1 conflict
0xdeaa385f…6b8b
0x34b655…2a6f
4 touches
1 conflict
0xf2f40f08…5cdb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity