← previous blocknext block →recent activity

Analyzing

Block #74,311,129

16 transactions · 10 stateful · 2026-05-13 11:27:25 UTC

Parallelism

81/100

Blocked

30%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,311,129  ·  16 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

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x3e4dfd22…1f91

0x34b655…2a6f

4 touches
1 conflict

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x2e2214a9…fe0d

0x5d823e…89c6

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x5d823e…89c6

4 touches
1 conflict

0x50997ada…364d

0x5d823e…89c6

4 touches
1 conflict

0xf0f673fd…37a7

0x5d823e…89c6

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: 0xc8689a47…62ee79

1 conflict on slot 0x6b3190712e…20a105

← previous block·next block →recent activity