← previous blocknext block →recent activity

Analyzing

Block #88,088,113

27 transactions · 24 stateful · 2026-07-16 07:45:15 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

1.15

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #88,088,113  ·  27 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x52b477bc…7ccf

0x34b655…2a6f

4 touches
1 conflict

0x574a8378…b246

0x34b655…2a6f

4 touches
1 conflict

0x5aff4cb3…c162

0x34b655…2a6f

4 touches
1 conflict

0x8eef368f…aa21

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

15 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity