← previous blocknext block →recent activity

Analyzing

Block #74,257,236

9 transactions · 8 stateful · 2026-05-13 05:28:55 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,257,236  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x6fe7bf93…0d0c

0x699abc…6a3b

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x5c8c7a0d…853f

0x699abc…6a3b

3 touches
1 conflict

0x21d5695a…a023

0x1c921c…0f5b

2 touches
0 conflicts

0x5860c4f3…0c39

0x3bd359…433a

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

2 touches
0 conflicts

0x0fc41e7b…6831

0x98dc6e…8633

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: 0x699abc15…c86a3b

1 conflict on slot 0x6fe7bf933e…ab0d0c

← previous block·next block →recent activity