← previous blocknext block →recent activity

Analyzing

Block #74,360,184

22 transactions · 16 stateful · 2026-05-13 16:53:35 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,360,184  ·  22 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

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x981bcc47…67c3

0x065c9d…c394

4 touches
1 conflict

0x9b353507…1932

0x065c9d…c394

4 touches
1 conflict

0xb5f55926…80a3

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

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