← previous blocknext block →recent activity

Analyzing

Block #74,266,393

13 transactions · 11 stateful · 2026-05-13 06:29:46 UTC

Parallelism

69/100

Blocked

36%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,266,393  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x194f2c02…19e6

0x2a68ba…90c5

2 touches
0 conflicts

0xdbadf6b0…43b2

0x33176b…e078

2 touches
0 conflicts

0x070a562a…8147

0x34b655…2a6f

2 touches
0 conflicts

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x413fbfa6…e2e7

0x34b655…2a6f

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: 0x681e908b…e1ae09

6 conflicts on slot 0x0d622e34f9…000000

← previous block·next block →recent activity