← previous blocknext block →recent activity

Analyzing

Block #88,359,739

19 transactions · 19 stateful · 2026-07-17 14:03:05 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #88,359,739  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x48cba2…b48b

6 touches
3 conflicts

0x1e166a45…98a7

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xc2ab3ad1…a6bc

0x34b655…2a6f

6 touches
3 conflicts

0xd5ab2f5b…092b

0x34b655…2a6f

4 touches
1 conflict

0x35a9f06c…7689

0x34b655…2a6f

4 touches
1 conflict

0x36890fff…f3d1

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: 0x48cba278…e2b48b

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity