← previous blocknext block →recent activity

Analyzing

Block #92,807,098

23 transactions · 21 stateful · 2026-08-03 15:11:25 UTC

Parallelism

74/100

Blocked

38%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,807,098  ·  23 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

0x34a1ee7e…fb20

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x7aa5d2c4…d6ef

0x34b655…2a6f

4 touches
1 conflict

0xab41643c…f9bf

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 0x34a1ee7e95…7cfb20

← previous block·next block →recent activity