← previous blocknext block →recent activity

Analyzing

Block #74,691,256

15 transactions · 14 stateful · 2026-05-15 05:45:47 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,691,256  ·  15 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

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x33a85821…52c2

0x065c9d…c394

3 touches
1 conflict

0x653acb35…c64f

0x065c9d…c394

3 touches
1 conflict

0xbdc813a1…7854

0x065c9d…c394

3 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

2 touches
0 conflicts

0x0eac6378…36f4

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: 0x065c9d28…a9c394

3 conflicts on slot 0x47b807a243…c53307

← previous block·next block →recent activity