← previous blocknext block →recent activity

Analyzing

Block #107,848,783

24 transactions · 22 stateful · 2026-09-25 08:45:45 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,848,783  ·  24 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

0xba522812…1f1f

0x34b655…2a6f

6 touches
3 conflicts

0x2b76a1fb…fdfc

0x34b655…2a6f

6 touches
3 conflicts

0x3a80bff1…7fa3

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x88e771e8…7d4a

0x34b655…2a6f

6 touches
3 conflicts

0x344b7f25…96dd

0x34b655…2a6f

4 touches
1 conflict

0x3f1ffe70…6105

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

3 conflicts on slot 0xba52281226…3a1f1f

← previous block·next block →recent activity