← previous blocknext block →recent activity

Analyzing

Block #74,613,197

21 transactions · 16 stateful · 2026-05-14 21:05:17 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,613,197  ·  21 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

0x0d0b2509…074d

0x3bd359…433a

10 touches
10 conflicts

0xe6455d1f…1029

0x754704…b603

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

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: 0x3bd359c1…15433a

10 conflicts on slot 0x0d0b2509ae…4b074d

← previous block·next block →recent activity