← previous blocknext block →recent activity
Analyzing
Block #87,713,306
58 transactions · 39 stateful · 2026-07-14 13:58:08 UTC
Parallelism
67/100
Blocked
72%
Avg conflicts / tx
2.9
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,713,306 · 58 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w28w19w010w114w015w130w531w632w733w834w935w1045w347w1449w1451w452w555w1656w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
20 touches
45 conflicts
0x0f8965bb…e238
0x34b655…2a6f
12 touches
15 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
12 touches
15 conflicts
0xa863a526…9995
0x34b655…2a6f
12 touches
15 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x767799cd…f423
0xc8689a…ee79
12 touches
15 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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity