← previous blocknext block →recent activity

Analyzing

Block #74,475,509

8 transactions · 7 stateful · 2026-05-14 05:41:13 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,475,509  ·  8 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

0x968bdacb…f461

0x2a68ba…90c5

4 touches
1 conflict

0x6b9cc025…c251

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0xeda2edc3…91d8

0x000000…012a

2 touches
0 conflicts

0x4020a2c0…5350

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x968bdacb8d…ddf461

← previous block·next block →recent activity