← previous blocknext block →recent activity

Analyzing

Block #74,436,436

17 transactions · 13 stateful · 2026-05-14 01:21:13 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,436,436  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x856b5c2e…8484

0x065c9d…c394

3 touches
1 conflict

0x648ab6e9…8fe5

0x065c9d…c394

3 touches
1 conflict

0xa810dfb7…4e97

0x065c9d…c394

3 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: 0x34b6552d…112a6f

3 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity