← previous blocknext block →recent activity
Analyzing
Block #87,723,984
44 transactions · 40 stateful · 2026-07-14 15:09:44 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
3.14
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,723,984 · 44 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w07w08w19w210w311w412w513w616w717w818w919w1020w1121w122w823w125w228w931w1040w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…00c9
0x34b655…2a6f
14 touches
21 conflicts
0x50718952…7c75
0x34b655…2a6f
14 touches
21 conflicts
0x7525206c…fbd5
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x84d74093…7808
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity