← previous blocknext block →recent activity

Analyzing

Block #74,459,799

12 transactions · 8 stateful · 2026-05-14 03:56:46 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,459,799  ·  12 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

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x8f8f5d74…1ccf

0x065c9d…c394

4 touches
1 conflict

0x89b23e6a…6181

0x699abc…6a3b

4 touches
1 conflict

0x874e8ac8…c2de

0x699abc…6a3b

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xba5743c7…21c3

0x1b6862…e19c

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…000013

← previous block·next block →recent activity