← previous blocknext block →recent activity

Analyzing

Block #74,410,564

13 transactions · 10 stateful · 2026-05-13 22:29:03 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,410,564  ·  13 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

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x34534d38…3b7c

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x45064d6b…bce9

0x371c7e…2f07

2 touches
0 conflicts

0xd1f92102…fdae

0x371c7e…2f07

2 touches
0 conflicts

0xd5c77fce…5df6

0x371c7e…2f07

2 touches
0 conflicts

0x8be2a8b2…91f2

0x3bd359…433a

2 touches
0 conflicts

0xc769eaf6…424e

0x3bd359…433a

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: 0x754704bc…afb603

1 conflict on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity