← previous blocknext block →recent activity

Analyzing

Block #74,204,497

16 transactions · 12 stateful · 2026-05-12 23:38:16 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,204,497  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbb25c4d1…fc50

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xb9d2cf20…a668

0x34b655…2a6f

4 touches
1 conflict

0xea9082f4…04a2

0x3bd359…433a

2 touches
0 conflicts

0x16005c59…cd79

0x754704…b603

2 touches
0 conflicts

0x4e368b2b…09ac

0x754704…b603

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity