← previous blocknext block →recent activity

Analyzing

Block #74,197,115

6 transactions · 6 stateful · 2026-05-12 22:49:14 UTC

Parallelism

50/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,197,115  ·  6 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfe20cb8f…f03d

0x34b655…2a6f

4 touches
1 conflict

0x8e2d8fe4…d729

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x7b7bcac3…8fbf

0x34b655…2a6f

4 touches
1 conflict

0x3bdab090…c5bf

0x34b655…2a6f

2 touches
0 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

2 touches
0 conflicts

0x41d3bfa5…523e

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity