← previous blocknext block →recent activity

Analyzing

Block #75,098,545

12 transactions · 5 stateful · 2026-05-17 03:06:03 UTC

Parallelism

83/100

Blocked

20%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,098,545  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x650861a7…68d9

0x065c9d…c394

3 touches
1 conflict

0xb4c3563e…e918

0x065c9d…c394

3 touches
1 conflict

0x0e41e016…fdf2

0x065c9d…c394

2 touches
0 conflicts

0x0ee5f2bb…61ae

0x065c9d…c394

2 touches
0 conflicts

0x20e040d8…2427

0x065c9d…c394

2 touches
0 conflicts

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x68d62fb2…4ed6

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 0x0000000000…00003d

← previous block·next block →recent activity