← previous blocknext block →recent activity

Analyzing

Block #102,244,286

25 transactions · 22 stateful · 2026-09-05 17:30:04 UTC

Parallelism

84/100

Blocked

32%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,244,286  ·  25 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0x08399ab6…0057

0x34b655…2a6f

4 touches
1 conflict

0x25fd5528…ff50

0x34b655…2a6f

4 touches
1 conflict

0x7c93b38a…9e69

0x34b655…2a6f

4 touches
1 conflict

0x81afdf2b…44fd

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity