← previous blocknext block →recent activity

Analyzing

Block #84,489,105

18 transactions · 17 stateful · 2026-06-29 15:12:58 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,489,105  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x4e1ce17e…98a7

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x286711a5…b3bf

0x34b655…2a6f

4 touches
1 conflict

0x344cbc15…66aa

0x34b655…2a6f

4 touches
1 conflict

0x3c906a94…4fae

0x34b655…2a6f

4 touches
1 conflict

0x3e505a15…70f8

0x34b655…2a6f

4 touches
1 conflict

0x75291f8b…3ac0

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity