← previous blocknext block →recent activity

Analyzing

Block #74,210,084

16 transactions · 11 stateful · 2026-05-13 00:15:22 UTC

Parallelism

56/100

Blocked

55%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,210,084  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x9d900b8a…1740

0xd32edf…ff58

3 touches
1 conflict

0x8437e96b…fe65

0x065c9d…c394

3 touches
1 conflict

0x40dff612…7f61

0x065c9d…c394

2 touches
0 conflicts

0x674fa8cc…de7b

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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: 0x065c9d28…a9c394

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity