← previous blocknext block →recent activity

Analyzing

Block #84,570,042

23 transactions · 22 stateful · 2026-06-30 00:13:16 UTC

Parallelism

78/100

Blocked

36%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,570,042  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x70638c24…1553

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xd637b3…4160

6 touches
3 conflicts

0x24227bc5…cb16

0x34b655…2a6f

4 touches
1 conflict

0x260889f6…d2f6

0x34b655…2a6f

4 touches
1 conflict

0x26918bca…6c75

0x34b655…2a6f

4 touches
1 conflict

0x27d815d2…5ca9

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 0x70638c2476…811553

← previous block·next block →recent activity