← previous blocknext block →recent activity

Analyzing

Block #92,109,978

16 transactions · 16 stateful · 2026-08-01 04:44:02 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,109,978  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x43a82efb…51c8

0x34b655…2a6f

4 touches
1 conflict

0x4d0252db…9ddb

0x34b655…2a6f

4 touches
1 conflict

0x6b2ba712…0214

0x34b655…2a6f

4 touches
1 conflict

0x9a8af3c2…e4ae

0x34b655…2a6f

4 touches
1 conflict

0x9cf9008a…d826

0x34b655…2a6f

4 touches
1 conflict

0xa0f935db…1717

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 0x482471adbb…39122f

← previous block·next block →recent activity