← previous blocknext block →recent activity

Analyzing

Block #83,453,875

18 transactions · 16 stateful · 2026-06-24 20:11:11 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #83,453,875  ·  18 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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0x8b61212e…558e

0x34b655…2a6f

6 touches
3 conflicts

0x2d95c7ff…1596

0x34b655…2a6f

6 touches
3 conflicts

0x022f72c3…07b6

0xc8689a…ee79

4 touches
1 conflict

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0x09a4820b…2db8

0x34b655…2a6f

4 touches
1 conflict

0x17eec3a0…44a4

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

3 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity