← previous blocknext block →recent activity

Analyzing

Block #74,425,368

13 transactions · 13 stateful · 2026-05-14 00:07:31 UTC

Parallelism

77/100

Blocked

31%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,425,368  ·  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

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0xbfe7fd3a…3168

0x3bd359…433a

4 touches
1 conflict

0x80a6e76c…277f

0x34b655…2a6f

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0x2d360b55…d4f5

0x80f006…d585

4 touches
1 conflict

0x2d360b55…d4f6

0x80f006…d585

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x7592c6f5…2824

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: 0x34b6552d…112a6f

1 conflict on slot 0xb245fe3647…73d765

← previous block·next block →recent activity