← previous blocknext block →recent activity

Analyzing

Block #72,496,396

6 transactions · 5 stateful · 2026-05-05 01:49:16 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,496,396  ·  6 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

0xf0aeb96a…ebca

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4b5ecdbd…07fd

0x065c9d…c394

3 touches
1 conflict

0xca14940c…f9b7

0x065c9d…c394

3 touches
1 conflict

0x33b19b24…0b55

0x065c9d…c394

2 touches
0 conflicts

0x452c8517…3974

0x065c9d…c394

2 touches
0 conflicts

0x62360ee4…9af3

0x065c9d…c394

2 touches
0 conflicts

0x8a28d5ac…c0ef

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 0xf0aeb96ade…e0ebca

← previous block·next block →recent activity