← previous blocknext block →recent activity

Analyzing

Block #83,946,621

16 transactions · 14 stateful · 2026-06-27 02:58:31 UTC

Parallelism

75/100

Blocked

57%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,946,621  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x40c49f…2af0

6 touches
3 conflicts

0xdfc5f346…7b42

0x40c49f…2af0

6 touches
3 conflicts

0x178fe051…465a

0x34b655…2a6f

4 touches
1 conflict

0x2bd0884d…47c9

0x34b655…2a6f

4 touches
1 conflict

0x2c539d94…b63a

0x34b655…2a6f

4 touches
1 conflict

0x3d34f2bd…5d63

0x34b655…2a6f

4 touches
1 conflict

0x4d63bc0a…65d8

0x34b655…2a6f

4 touches
1 conflict

0x4f4bdabd…ffba

0x34b655…2a6f

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: 0x40c49f17…d22af0

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity