← previous blocknext block →recent activity

Analyzing

Block #88,194,814

17 transactions · 16 stateful · 2026-07-16 19:39:54 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.82

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,194,814  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x1803586e…d149

0xa6afd3…d132

4 touches
1 conflict

0x24ca1902…7a87

0x34b655…2a6f

4 touches
1 conflict

0x4dc6cd61…f674

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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: Perpl

3 conflicts on slot 0x4acbdbcf7f…d0a8c6

← previous block·next block →recent activity