← previous blocknext block →recent activity
Analyzing
Block #87,794,307
34 transactions · 27 stateful · 2026-07-14 23:00:10 UTC
Parallelism
59/100
Blocked
56%
Avg conflicts / tx
2.15
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,794,307 · 34 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
1w05w110w011w112w213w314w415w516w617w721w823w925w1027w230w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9465204c…bf37
0x34b655…2a6f
22 touches
55 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
18 touches
36 conflicts
0x28c62bca…b746
0x34b655…2a6f
16 touches
28 conflicts
0x9ae859db…2d84
0x34b655…2a6f
16 touches
28 conflicts
0x805d08cf…3cfc
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x3726966a…669d
0x34b655…2a6f
15 touches
28 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
55 conflicts on slot 0x9465204cd8…debf37
Audit this contract →
← previous block·next block →recent activity