← previous blocknext block →recent activity

Analyzing

Block #74,252,775

14 transactions · 13 stateful · 2026-05-13 04:59:16 UTC

Parallelism

79/100

Blocked

23%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,252,775  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x768cffcd…2648

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x5d70606a…1d53

0x34b655…2a6f

4 touches
1 conflict

0xbb12db23…857e

0x34b655…2a6f

4 touches
1 conflict

0x60d12eae…8c18

0x065c9d…c394

2 touches
0 conflicts

0x72e8e3a3…d31b

0x065c9d…c394

2 touches
0 conflicts

0xb2253771…8b0b

0x065c9d…c394

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

3 conflicts on slot 0x768cffcdb0…d12648

← previous block·next block →recent activity