← previous blocknext block →recent activity

Analyzing

Block #72,095,055

13 transactions · 11 stateful · 2026-05-03 05:08:32 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,095,055  ·  13 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

0x00000000…0002

0x7e9d3a…9fda

6 touches
3 conflicts

0xde03f742…15d9

0x065c9d…c394

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0x183b7456…e175

0x34b655…2a6f

2 touches
0 conflicts

0x3254d19b…f714

0x34b655…2a6f

2 touches
0 conflicts

0x3347cbe5…846c

0x34b655…2a6f

2 touches
0 conflicts

0x414e9446…4b59

0x34b655…2a6f

2 touches
0 conflicts

0x4ac5588f…e61f

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: 0x7e9d3a8a…4f9fda

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity