← previous blocknext block →recent activity

Analyzing

Block #83,941,166

19 transactions · 17 stateful · 2026-06-27 02:22:06 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,941,166  ·  19 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

0x785889c9…0603

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0b16149e…7d4d

0x065c9d…c394

6 touches
3 conflicts

0xa49be8c6…0267

0x34b655…2a6f

6 touches
3 conflicts

0x76477ddf…b8f8

0xc8689a…ee79

4 touches
1 conflict

0x7362e560…4054

0x065c9d…c394

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: Perpl

3 conflicts on slot 0x785889c9fb…160603

← previous block·next block →recent activity