← previous blocknext block →recent activity

Analyzing

Block #73,161,841

27 transactions · 23 stateful · 2026-05-08 03:41:08 UTC

Parallelism

63/100

Blocked

70%

Avg conflicts / tx

1.93

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,161,841  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x388e001a…7e04

0x34b655…2a6f

14 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0x578e7f66…1b56

0x34b655…2a6f

10 touches
10 conflicts

0x602ff3d4…3ebd

0x34b655…2a6f

10 touches
10 conflicts

0xa7a586ac…c700

0x34b655…2a6f

10 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 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

21 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity