← previous blocknext block →recent activity

Analyzing

Block #74,326,313

7 transactions · 6 stateful · 2026-05-13 13:08:24 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,326,313  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x5e9a6588…01d2

0x34b655…2a6f

4 touches
1 conflict

0x62e20208…be65

0x0555e3…2b9c

2 touches
0 conflicts

0x6677f92f…b7cd

0x0555e3…2b9c

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0xe465746a…db9b

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0000

0x094452…0a09

2 touches
0 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

1 conflict on slot 0x2877f4400c…13c2c8

← previous block·next block →recent activity