← previous blocknext block →recent activity

Analyzing

Block #73,478,086

12 transactions · 10 stateful · 2026-05-09 14:45:31 UTC

Parallelism

75/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,478,086  ·  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

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xc69c1b2f…78f0

0x065c9d…c394

3 touches
1 conflict

0x42fb8a13…7e02

0x065c9d…c394

2 touches
0 conflicts

0x7067228e…8c75

0x065c9d…c394

2 touches
0 conflicts

0x87259dbb…c4f3

0x065c9d…c394

2 touches
0 conflicts

0xaf370227…f180

0x065c9d…c394

2 touches
0 conflicts

0xb24baff0…e36b

0x065c9d…c394

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

1 conflict on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity