← previous blocknext block →recent activity

Analyzing

Block #84,287,503

16 transactions · 13 stateful · 2026-06-28 16:49:10 UTC

Parallelism

88/100

Blocked

15%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #84,287,503  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x6f58168d…ea24

0x34b655…2a6f

4 touches
1 conflict

0x7506443a…4820

0x34b655…2a6f

4 touches
1 conflict

0x81c5483a…59e8

0x34b655…2a6f

4 touches
1 conflict

0xad9c8208…8b1c

0x34b655…2a6f

4 touches
1 conflict

0xd7513857…4c08

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf4a79d55…3f4f

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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

1 conflict on slot 0x6f58168d48…e3ea24

← previous block·next block →recent activity