← previous blocknext block →recent activity

Analyzing

Block #74,762,813

40 transactions · 33 stateful · 2026-05-15 13:43:54 UTC

Parallelism

70/100

Blocked

64%

Avg conflicts / tx

1.65

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,762,813  ·  40 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

16 touches
28 conflicts

0xb9868b52…c77f

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

10 touches
10 conflicts

0x388e001a…7e04

0x34b655…2a6f

8 touches
6 conflicts

0x443a3e47…f4a4

0x065c9d…c394

8 touches
6 conflicts

0xfd784183…67bb

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity