← previous blocknext block →recent activity

Analyzing

Block #73,297,269

12 transactions · 9 stateful · 2026-05-08 18:42:23 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,297,269  ·  12 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

0xecd87a39…d9c5

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x445b51c5…0be4

0x34b655…2a6f

3 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0xb96e29a5…0419

0x34b655…2a6f

2 touches
0 conflicts

0xc3aacf13…6b3d

0x34b655…2a6f

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

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

1 conflict on slot 0xecd87a399c…10d9c5

← previous block·next block →recent activity