← previous blocknext block →recent activity

Analyzing

Block #72,496,254

12 transactions · 10 stateful · 2026-05-05 01:48:19 UTC

Parallelism

83/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x3eadb0b6…d2f7

0x34b655…2a6f

4 touches
1 conflict

0x5d32a251…d929

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x1179284b…db76

0x34b655…2a6f

4 touches
1 conflict

0x1f8e441d…85b7

0x2ab50b…5c41

2 touches
0 conflicts

0x25cfe585…79a0

0x2ab50b…5c41

2 touches
0 conflicts

0x288e4d6c…ea0b

0x2ab50b…5c41

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 0x3eadb0b696…e8d2f7

← previous block·next block →recent activity