← previous blocknext block →recent activity

Analyzing

Block #74,216,114

19 transactions · 16 stateful · 2026-05-13 00:55:32 UTC

Parallelism

68/100

Blocked

38%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,216,114  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x11a67036…1c34

0x065c9d…c394

4 touches
1 conflict

0x65b4bfb0…8e6c

0x065c9d…c394

2 touches
0 conflicts

0x6fb60269…489c

0x065c9d…c394

2 touches
0 conflicts

0x9345cae5…94a4

0x065c9d…c394

2 touches
0 conflicts

0xce75b07f…cfd9

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity