← previous blocknext block →recent activity

Analyzing

Block #74,336,184

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

Parallelism

81/100

Blocked

18%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,336,184  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xe5adcaa3…cd20

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0000

0x04ddf6…7f33

2 touches
0 conflicts

0x00000000…0002

0x04ddf6…7f33

2 touches
0 conflicts

0x00000000…0003

0x04ddf6…7f33

2 touches
0 conflicts

0x00000000…0008

0x04ddf6…7f33

2 touches
0 conflicts

0x4f4d61e8…ed82

0x065c9d…c394

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

1 conflict on slot 0xe5adcaa337…12cd20

← previous block·next block →recent activity