← previous blocknext block →recent activity

Analyzing

Block #92,188,845

17 transactions · 15 stateful · 2026-08-01 11:20:42 UTC

Parallelism

82/100

Blocked

47%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,188,845  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x534ef679…ae9d

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x00ebed49…1e8f

0x34b655…2a6f

6 touches
3 conflicts

0x083ff337…401b

0x34b655…2a6f

4 touches
1 conflict

0x09a51882…159c

0x34b655…2a6f

4 touches
1 conflict

0x19439a65…eb51

0x34b655…2a6f

4 touches
1 conflict

0x1951ee47…540f

0x34b655…2a6f

4 touches
1 conflict

0x2979e2dd…335e

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

3 conflicts on slot 0x534ef679c5…43ae9d

← previous block·next block →recent activity