← previous blocknext block →recent activity
Analyzing
Block #86,624,045
48 transactions · 42 stateful · 2026-07-09 12:34:19 UTC
Parallelism
67/100
Blocked
62%
Avg conflicts / tx
1.98
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,624,045 · 48 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w111w212w013w114w215w319w020w121w222w323w424w525w627w330w431w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xa29182a1…c12c
0x34b655…2a6f
10 touches
10 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
10 touches
10 conflicts
0xb43dc900…22f2
0xa6afd3…d132
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity