← previous blocknext block →recent activity
Analyzing
Block #87,497,627
42 transactions · 35 stateful · 2026-07-13 13:55:00 UTC
Parallelism
67/100
Blocked
69%
Avg conflicts / tx
1.88
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,497,627 · 42 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
1w02w03w04w15w16w27w210w011w118w119w220w321w422w523w624w725w827w328w431w932w233w136w138w1139w1240w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x24d68cf2…09b7
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x7b2f3e6d…978f
0x34b655…2a6f
10 touches
10 conflicts
0x4e1ce17e…98a7
0x34b655…2a6f
10 touches
10 conflicts
0x76a4ddec…8476
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
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