← previous blocknext block →recent activity
Analyzing
Block #86,513,642
20 transactions · 15 stateful · 2026-07-09 00:14:43 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,513,642 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w09w110w216w317w418w519w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
10 touches
10 conflicts
0x9379391f…caa2
0x34b655…2a6f
6 touches
3 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
6 touches
3 conflicts
0xdf6fce37…9b58
0x34b655…2a6f
6 touches
3 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity