← previous blocknext block →recent activity

Analyzing

Block #84,514,238

27 transactions · 17 stateful · 2026-06-29 18:00:42 UTC

Parallelism

78/100

Blocked

53%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #84,514,238  ·  27 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0x9672a430…3356

0x34b655…2a6f

6 touches
3 conflicts

0xa8279ae9…f9f9

0x34b655…2a6f

4 touches
1 conflict

0xb6ed511f…6b68

0x34b655…2a6f

4 touches
1 conflict

0xbe9e904e…93bf

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd2b6674b…78dc

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: Kuru Exchange: MarginAccount

10 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity