← previous blocknext block →recent activity

Analyzing

Block #72,036,681

16 transactions · 12 stateful · 2026-05-02 22:39:57 UTC

Parallelism

81/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,036,681  ·  16 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

0x1c913164…5c2e

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xb6818fd3…c885

0x34b655…2a6f

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

0x5ba51e87…44ee

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

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 0x1c913164f5…845c2e

← previous block·next block →recent activity