← previous blocknext block →recent activity
Analyzing
Block #87,723,223
48 transactions · 39 stateful · 2026-07-14 15:04:38 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
2.21
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,723,223 · 48 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
1w02w17w08w111w012w113w015w117w018w119w220w321w422w523w624w725w826w927w1031w132w233w235w336w444w1145w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x7525206c…fbd5
0x34b655…2a6f
20 touches
45 conflicts
0x84d74093…7808
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x0dd44476…ef40
0x34b655…2a6f
12 touches
15 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