← previous blocknext block →recent activity

Analyzing

Block #107,849,478

23 transactions · 21 stateful · 2026-09-25 08:49:15 UTC

Parallelism

65/100

Blocked

48%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #107,849,478  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd95ed05c…acca

0x34b655…2a6f

12 touches
15 conflicts

0x2b76a1fb…fdfc

0x34b655…2a6f

12 touches
15 conflicts

0xcb21158b…f18d

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0xf75c3a6b…0568

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xbac338fb…5aec

0x34b655…2a6f

6 touches
3 conflicts

0xc4c059d8…185d

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0xd95ed05c37…48acca

← previous block·next block →recent activity