← previous blocknext block →recent activity

Analyzing

Block #74,255,181

14 transactions · 9 stateful · 2026-05-13 05:15:16 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,255,181  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xfbbc35e2…f66b

0x34b655…2a6f

4 touches
1 conflict

0x9df8469b…89b3

0x34b655…2a6f

4 touches
1 conflict

0xaa0d0542…d8ec

0x34b655…2a6f

4 touches
1 conflict

0xc108f63d…204f

0x34b655…2a6f

4 touches
1 conflict

0xfb790f01…fea9

0x34b655…2a6f

4 touches
1 conflict

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x1b9e654e…0a08

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity