← previous blocknext block →recent activity
Analyzing
Block #87,714,363
45 transactions · 32 stateful · 2026-07-14 14:05:15 UTC
Parallelism
69/100
Blocked
66%
Avg conflicts / tx
1.69
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,714,363 · 45 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
1w02w13w04w07w08w19w213w014w122w223w324w425w526w633w1034w1135w1236w138w1340w241w143w1144w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xe214f7d0…5600
0x34b655…2a6f
12 touches
15 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xb94312c7…10e3
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity