← previous blocknext block →recent activity

Analyzing

Block #73,324,214

13 transactions · 8 stateful · 2026-05-08 21:41:45 UTC

Parallelism

85/100

Blocked

13%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,324,214  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x43c764bf…6216

0xa6afd3…d132

4 touches
1 conflict

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x1b9e654e…0a08

0x34b655…2a6f

2 touches
0 conflicts

0x23951077…539b

0x34b655…2a6f

2 touches
0 conflicts

0x280d1119…ee4d

0x34b655…2a6f

2 touches
0 conflicts

0x28933977…81c5

0x34b655…2a6f

2 touches
0 conflicts

0x2fe4467b…dd70

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: 0xa6afd386…b0d132

1 conflict on slot 0x43c764bf1a…bb6216

← previous block·next block →recent activity