← previous blocknext block →recent activity

Analyzing

Block #74,223,836

13 transactions · 10 stateful · 2026-05-13 01:46:54 UTC

Parallelism

54/100

Blocked

50%

Avg conflicts / tx

1.15

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,223,836  ·  13 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

0xf823e97f…2ee6

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xc60dbadf…29a9

0x065c9d…c394

3 touches
1 conflict

0xdbadf6b0…43b2

0x33176b…e078

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

2 touches
0 conflicts

0x5b571ba0…f13a

0x368ee5…7ca4

2 touches
0 conflicts

0x68faa0b9…14af

0x368ee5…7ca4

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