← previous blocknext block →recent activity
Analyzing
Block #87,723,188
39 transactions · 35 stateful · 2026-07-14 15:04:24 UTC
Parallelism
49/100
Blocked
71%
Avg conflicts / tx
5.38
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,723,188 · 39 txs across 20 waves · depth 20
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
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w18w29w310w411w512w613w714w815w916w1017w1129w930w1031w1134w1035w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
38 touches
171 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x84d74093…7808
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x0dd44476…ef40
0x34b655…2a6f
16 touches
28 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x7525206c…fbd5
0x34b655…2a6f
16 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
171 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity