← previous blocknext block →recent activity
Analyzing
Block #87,590,113
22 transactions · 20 stateful · 2026-07-14 00:14:22 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,590,113 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w29w312w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206fb8db…a146
0x34b655…2a6f
14 touches
21 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
12 touches
15 conflicts
0x5170a218…3a84
0xc8689a…ee79
12 touches
15 conflicts
0x39c4bc47…ce30
0x34b655…2a6f
12 touches
15 conflicts
0x63c900f4…2600
0x34b655…2a6f
12 touches
15 conflicts
0xad0c7701…1d83
0x34b655…2a6f
12 touches
15 conflicts
0xc2186704…5cc3
0x34b655…2a6f
12 touches
15 conflicts
0x16ac5b24…69b8
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x206fb8db95…b8a146
Audit this contract →
← previous block·next block →recent activity