← previous blocknext block →recent activity

Analyzing

Block #92,543,771

19 transactions · 19 stateful · 2026-08-02 17:05:42 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,543,771  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x19840da5…08b8

0x34b655…2a6f

4 touches
1 conflict

0x19b4e3fd…3821

0x34b655…2a6f

4 touches
1 conflict

0x2d7ea048…d78e

0x34b655…2a6f

4 touches
1 conflict

0x3c7c65d0…0b52

0x34b655…2a6f

4 touches
1 conflict

0x3eacdae2…6436

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity