← previous blocknext block →recent activity
Analyzing
Block #87,731,696
38 transactions · 31 stateful · 2026-07-14 16:01:19 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
2.42
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,731,696 · 38 txs across 14 waves · depth 14
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
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w08w114w015w116w217w318w419w520w621w722w823w925w526w1029w330w231w336w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xa55c4598…2988
0x34b655…2a6f
14 touches
21 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0x6a5b8b80…09a3
0x34b655…2a6f
10 touches
10 conflicts
0x747f609d…1555
0x34b655…2a6f
10 touches
10 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity