← previous blocknext block →recent activity
Analyzing
Block #87,497,084
41 transactions · 31 stateful · 2026-07-13 13:51:22 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
2.44
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,497,084 · 41 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w314w015w116w123w224w325w426w528w731w732w833w934w1035w436w1138w1239w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x326d4924…1788
0x34b655…2a6f
14 touches
21 conflicts
0xfdd655b8…bf89
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0xc807a400…b958
0x34b655…2a6f
10 touches
10 conflicts
0xc879978e…3e50
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
36 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity