← previous blocknext block →recent activity

Analyzing

Block #74,586,167

26 transactions · 20 stateful · 2026-05-14 18:04:19 UTC

Parallelism

77/100

Blocked

55%

Avg conflicts / tx

0.96

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,586,167  ·  26 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

10 touches
10 conflicts

0xbad68552…e6bf

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x8d0e98f3…7ba0

0x34b655…2a6f

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0x20bc61fa…7d46

0xd32edf…ff58

5 touches
3 conflicts

0xff57dec4…6482

0x34b655…2a6f

5 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

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: 0x34b6552d…112a6f

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity