← previous blocknext block →recent activity

Analyzing

Block #88,139,693

21 transactions · 16 stateful · 2026-07-16 13:30:20 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,139,693  ·  21 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

0x250c3574…21db

0x851145…3f07

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0888d42d…3685

0x34b655…2a6f

4 touches
1 conflict

0x671bc7c1…3251

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0xf06cb710…1a9a

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x7e5ea60a…c4aa

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: 0x851145ea…9f3f07

1 conflict on slot 0x250c3574a4…ad21db

← previous block·next block →recent activity