← previous blocknext block →recent activity

Analyzing

Block #74,252,798

9 transactions · 8 stateful · 2026-05-13 04:59:25 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,252,798  ·  9 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

4 touches
1 conflict

0xbb12db23…857e

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x4e33eaf5…cec7

0x065c9d…c394

2 touches
0 conflicts

0xc3686839…e8d5

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

2 touches
0 conflicts

0xf823e97f…2ee6

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

1 conflict on slot 0x768cffcdb0…d12648

← previous block·next block →recent activity