← previous blocknext block →recent activity

Analyzing

Block #84,509,796

29 transactions · 20 stateful · 2026-06-29 17:31:03 UTC

Parallelism

76/100

Blocked

45%

Avg conflicts / tx

0.76

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #84,509,796  ·  29 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0xacbc3fbb…fe8e

0x34b655…2a6f

12 touches
15 conflicts

0xa6f7ec90…7bc9

0x34b655…2a6f

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0xef65bff3…7c9d

0x2a68ba…90c5

8 touches
6 conflicts

0x158accef…4c74

0xa6afd3…d132

8 touches
6 conflicts

0xe41f8863…29a4

0xa6afd3…d132

8 touches
6 conflicts

0xdf708ee7…1fcf

0xc8689a…ee79

8 touches
6 conflicts

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

15 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity