← previous blocknext block →recent activity
Analyzing
Block #86,670,501
40 transactions · 33 stateful · 2026-07-09 17:45:54 UTC
Parallelism
65/100
Blocked
70%
Avg conflicts / tx
3.08
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #86,670,501 · 40 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w27w310w011w112w213w314w415w516w617w718w819w920w1021w1122w1224w328w1029w337w1138w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
14 touches
21 conflicts
0x70ff9262…8d80
0x34b655…2a6f
12 touches
15 conflicts
0x3c78ca04…432c
0x34b655…2a6f
8 touches
6 conflicts
0x5d537073…cf27
0x34b655…2a6f
8 touches
6 conflicts
0x5f72d58f…c445
0x34b655…2a6f
8 touches
6 conflicts
0x70b87e4d…65d5
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity