← previous blocknext block →recent activity

Analyzing

Block #88,087,345

18 transactions · 15 stateful · 2026-07-16 07:40:08 UTC

Parallelism

50/100

Blocked

73%

Avg conflicts / tx

1.89

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #88,087,345  ·  18 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0x5777bd87…71bd

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6c60fbcf…8744

0x34b655…2a6f

4 touches
1 conflict

0x744e0a36…70f7

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4a3

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4a4

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity