← previous blocknext block →recent activity

Analyzing

Block #74,183,107

21 transactions · 19 stateful · 2026-05-12 21:16:02 UTC

Parallelism

52/100

Blocked

68%

Avg conflicts / tx

2

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,183,107  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0xf823e97f…2ee6

0x065c9d…c394

10 touches
10 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

8 touches
6 conflicts

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0xb48ada7b…3e2a

0x34b655…2a6f

4 touches
1 conflict

0x59a54ff4…d21b

0x34b655…2a6f

4 touches
1 conflict

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

21 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity