← previous blocknext block →recent activity

Analyzing

Block #74,224,852

19 transactions · 17 stateful · 2026-05-13 01:53:38 UTC

Parallelism

74/100

Blocked

53%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,224,852  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe6455d1f…1029

0x754704…b603

10 touches
10 conflicts

0x0d0b2509…074d

0x3bd359…433a

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0x9288e471…c99b

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

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: 0x754704bc…afb603

10 conflicts on slot 0xe6455d1fbe…eb1029

← previous block·next block →recent activity