← previous blocknext block →recent activity

Analyzing

Block #74,210,083

13 transactions · 10 stateful · 2026-05-13 00:15:22 UTC

Parallelism

77/100

Blocked

20%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,210,083  ·  13 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x1066aad0…b22d

0x065c9d…c394

4 touches
1 conflict

0x11b4eb92…8df6

0x065c9d…c394

3 touches
1 conflict

0x987da054…0fcc

0x065c9d…c394

3 touches
1 conflict

0x194f2c02…19e6

0x2a68ba…90c5

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x20ac0567…c954

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity