← previous blocknext block →recent activity

Analyzing

Block #74,215,425

13 transactions · 10 stateful · 2026-05-13 00:50:55 UTC

Parallelism

77/100

Blocked

20%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x768cffcd…2648

0x34b655…2a6f

6 touches
3 conflicts

0xc166a323…1f33

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x75f928fc…0465

0x34b655…2a6f

4 touches
1 conflict

0x4af638b5…fdfd

0x34b655…2a6f

4 touches
1 conflict

0x73f4551d…4188

0x34b655…2a6f

2 touches
0 conflicts

0x8b8e4020…11b0

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 0x768cffcdb0…d12648

← previous block·next block →recent activity