← previous blocknext block →recent activity
Analyzing
Block #87,731,481
60 transactions · 52 stateful · 2026-07-14 15:59:53 UTC
Parallelism
72/100
Blocked
69%
Avg conflicts / tx
2.88
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,731,481 · 60 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w110w312w013w114w215w317w019w020w121w222w323w431w432w533w634w735w836w947w1652w353w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0001
0xc1ff9f…b0fc
14 touches
21 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
14 touches
21 conflicts
0x52f7c71c…d0a6
0x34b655…2a6f
12 touches
15 conflicts
0xa55c4598…2988
0x34b655…2a6f
12 touches
15 conflicts
0x757b0543…e087
0x34b655…2a6f
12 touches
15 conflicts
0xf8145615…439e
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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity