← previous blocknext block →recent activity

Analyzing

Block #74,190,691

24 transactions · 11 stateful · 2026-05-12 22:06:24 UTC

Parallelism

83/100

Blocked

45%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,190,691  ·  24 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

0xb174f858…824a

0xd32edf…ff58

7 touches
6 conflicts

0x38b5b2ce…c5bb

0xfa32f9…f3f0

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0x2dcfcd19…ee89

0x699abc…6a3b

4 touches
1 conflict

0xd2a1c35f…9d5f

0x699abc…6a3b

4 touches
1 conflict

0x796f6020…2f77

0x754704…b603

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

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: 0xd32edf66…9fff58

6 conflicts on slot 0xb174f85860…82824a

← previous block·next block →recent activity