← previous blocknext block →recent activity

Analyzing

Block #72,036,941

7 transactions · 4 stateful · 2026-05-02 22:41:41 UTC

Parallelism

71/100

Blocked

25%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x11a41e46…f300

0x065c9d…c394

2 touches
0 conflicts

0x39badc9a…a7d0

0x065c9d…c394

2 touches
0 conflicts

0x3bf586a8…c153

0x065c9d…c394

2 touches
0 conflicts

0x6d6f76dd…de6c

0x065c9d…c394

2 touches
0 conflicts

0x92e544e2…ce1b

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: Kuru Exchange: Market-MON/USDC

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity