← previous blocknext block →recent activity

Analyzing

Block #74,509,794

19 transactions · 14 stateful · 2026-05-14 09:30:06 UTC

Parallelism

79/100

Blocked

43%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,509,794  ·  19 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

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9e719c7a…df63

0x34b655…2a6f

6 touches
3 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

4 touches
1 conflict

0x03b4fefa…9a00

0x34b655…2a6f

4 touches
1 conflict

0x041ee703…b4c1

0x34b655…2a6f

4 touches
1 conflict

0x78067279…d187

0x34b655…2a6f

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: Wrapped MON (WMON)

6 conflicts on slot 0xa472d565a0…ae9fe4

← previous block·next block →recent activity