← previous blocknext block →recent activity
Analyzing
Block #87,504,074
40 transactions · 32 stateful · 2026-07-13 14:38:09 UTC
Parallelism
65/100
Blocked
75%
Avg conflicts / tx
2.35
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,504,074 · 40 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
1w03w14w25w36w37w08w111w012w113w016w119w020w121w222w326w728w830w431w1032w233w134w237w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x3a6290da…e683
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…00c9
0x34b655…2a6f
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xc3688185…9b36
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xafb2524a…0ce4
0x34b655…2a6f
8 touches
6 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity