← previous blocknext block →recent activity

Analyzing

Block #73,204,847

12 transactions · 10 stateful · 2026-05-08 08:27:37 UTC

Parallelism

75/100

Blocked

20%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,204,847  ·  12 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

0xa5fb9779…2384

0x34b655…2a6f

6 touches
3 conflicts

0xf4730a2d…3538

0x34b655…2a6f

6 touches
3 conflicts

0xb91a6f59…722c

0x34b655…2a6f

4 touches
1 conflict

0xca0ac2d9…4aab

0x34b655…2a6f

4 touches
1 conflict

0x55b4ed22…fcc8

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0xa0b88c5d…c5b9

0x34b655…2a6f

2 touches
0 conflicts

0xd73e8c35…d0b5

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 0xa5fb977967…df2384

← previous block·next block →recent activity