← previous blocknext block →recent activity
Analyzing
Block #87,711,897
42 transactions · 33 stateful · 2026-07-14 13:48:43 UTC
Parallelism
69/100
Blocked
73%
Avg conflicts / tx
2.31
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,711,897 · 42 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w27w08w114w015w116w217w318w419w520w621w722w823w924w1025w1126w1227w231w432w134w338w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0x0e3e9dbd…7c82
0x34b655…2a6f
12 touches
15 conflicts
0xdbfbbbd3…dcb8
0x34b655…2a6f
10 touches
10 conflicts
0x7561f24a…4522
0x34b655…2a6f
6 touches
3 conflicts
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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity