← previous blocknext block →recent activity
Analyzing
Block #87,497,423
34 transactions · 32 stateful · 2026-07-13 13:53:38 UTC
Parallelism
50/100
Blocked
66%
Avg conflicts / tx
2.47
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,497,423 · 34 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
1w02w03w14w26w07w08w010w111w112w213w314w415w516w617w718w821w922w1024w1125w1227w129w130w1331w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xfd77e6c1…264b
0x34b655…2a6f
14 touches
21 conflicts
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0x571cb36d…3b3d
0x34b655…2a6f
10 touches
10 conflicts
0x43bc2389…898f
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0xa1002523…644f
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