← previous blocknext block →recent activity

Analyzing

Block #88,087,803

20 transactions · 20 stateful · 2026-07-16 07:43:12 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #88,087,803  ·  20 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

10 touches
10 conflicts

0x5777bd87…71bd

0x34b655…2a6f

6 touches
3 conflicts

0x10797f0b…439a

0x34b655…2a6f

4 touches
1 conflict

0x201679bc…0414

0x34b655…2a6f

4 touches
1 conflict

0x2b5101ac…090b

0x34b655…2a6f

4 touches
1 conflict

0x306233f2…96c3

0x34b655…2a6f

4 touches
1 conflict

0x3d158563…8713

0x34b655…2a6f

4 touches
1 conflict

0x3e711368…86f3

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity