← previous blocknext block →recent activity

Analyzing

Block #74,283,588

19 transactions · 17 stateful · 2026-05-13 08:24:06 UTC

Parallelism

89/100

Blocked

24%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,283,588  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x97f0b171…fc3d

0xd32edf…ff58

3 touches
1 conflict

0x2b3ec945…dde3

0x065c9d…c394

2 touches
0 conflicts

0x2b3ec945…dde4

0x065c9d…c394

2 touches
0 conflicts

0x7243b794…4405

0x065c9d…c394

2 touches
0 conflicts

0x74475d01…0e8e

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity