← previous blocknext block →recent activity

Analyzing

Block #74,762,006

20 transactions · 16 stateful · 2026-05-15 13:38:30 UTC

Parallelism

85/100

Blocked

19%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,762,006  ·  20 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

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0xdc683230…6df3

0x34b655…2a6f

4 touches
1 conflict

0x81741712…8314

0x065c9d…c394

3 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

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

3 conflicts on slot 0xb9868b5233…c6c77f

← previous block·next block →recent activity