← previous blocknext block →recent activity

Analyzing

Block #107,822,944

22 transactions · 19 stateful · 2026-09-25 06:35:42 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #107,822,944  ·  22 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

0x42522e76…2592

0x34b655…2a6f

10 touches
10 conflicts

0xa7ba83b5…d0a8

0x34b655…2a6f

10 touches
10 conflicts

0x9a8482cc…8bee

0x34b655…2a6f

6 touches
3 conflicts

0xccdc1094…8a94

0x34b655…2a6f

6 touches
3 conflicts

0xb195cffa…8098

0x34b655…2a6f

6 touches
3 conflicts

0x33f5cbc5…268b

0x34b655…2a6f

4 touches
1 conflict

0x3750b746…5a9e

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

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

10 conflicts on slot 0x42522e76ce…082592

← previous block·next block →recent activity