← previous blocknext block →recent activity

Analyzing

Block #74,686,554

18 transactions · 17 stateful · 2026-05-15 05:14:31 UTC

Parallelism

72/100

Blocked

29%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,686,554  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xa21e8abe…a7f1

0x34b655…2a6f

6 touches
3 conflicts

0x9b8800c1…ed12

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0xd5b70d…615b

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

4 touches
1 conflict

0x886f7fe6…8b7a

0x34b655…2a6f

4 touches
1 conflict

0x94a3fb3f…7515

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity