← previous blocknext block →recent activity

Analyzing

Block #83,694,343

13 transactions · 9 stateful · 2026-06-25 22:55:42 UTC

Parallelism

77/100

Blocked

22%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,694,343  ·  13 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

0xb6836671…5c3c

0x34b655…2a6f

6 touches
3 conflicts

0xfa1bbceb…dfed

0x34b655…2a6f

4 touches
1 conflict

0x562b8381…cef9

0x34b655…2a6f

4 touches
1 conflict

0x7b6d2deb…dde0

0x34b655…2a6f

4 touches
1 conflict

0x913ebf0e…d816

0x34b655…2a6f

4 touches
1 conflict

0xb1306d0a…44dc

0x34b655…2a6f

4 touches
1 conflict

0xbd68c7c7…40b3

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

3 conflicts on slot 0xb683667184…055c3c

← previous block·next block →recent activity