← previous blocknext block →recent activity
Analyzing
Block #87,727,380
35 transactions · 21 stateful · 2026-07-14 15:32:28 UTC
Parallelism
77/100
Blocked
52%
Avg conflicts / tx
0.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,727,380 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w115w218w020w121w222w323w424w526w132w633w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xc4de6652…13f4
0x34b655…2a6f
8 touches
6 conflicts
0xa1111a1a…f235
0x34b655…2a6f
8 touches
6 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
4 touches
1 conflict
0x78b5040c…2257
0x34b655…2a6f
4 touches
1 conflict
0x882f66cc…87d9
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity