← previous blocknext block →recent activity

Analyzing

Block #88,184,493

16 transactions · 14 stateful · 2026-07-16 18:30:40 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #88,184,493  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x9cf61590…ad8c

0x34b655…2a6f

4 touches
1 conflict

0xd4702f73…926c

0x34b655…2a6f

4 touches
1 conflict

0x508bbf1b…fe95

0x34b655…2a6f

4 touches
1 conflict

0xfb53ecf8…bd11

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x44fb0f8a…b7c4

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09d

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x92385428ad…dc6941

← previous block·next block →recent activity