← previous blocknext block →recent activity

Analyzing

Block #86,328,144

25 transactions · 23 stateful · 2026-07-08 03:35:22 UTC

Parallelism

72/100

Blocked

52%

Avg conflicts / tx

1.12

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,328,144  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…0002

0x04fdea…47d7

14 touches
21 conflicts

0x18cf3003…51d1

0x065c9d…c394

6 touches
3 conflicts

0xcc8faac2…c766

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x90ab3d60…2195

0x34b655…2a6f

4 touches
1 conflict

0x9a36cb2e…0929

0x34b655…2a6f

4 touches
1 conflict

0x9dd0a735…4d04

0x34b655…2a6f

4 touches
1 conflict

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: 0x04fdeac2…f747d7

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity