← previous blocknext block →recent activity

Analyzing

Block #105,618,614

20 transactions · 20 stateful · 2026-09-17 13:35:02 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,618,614  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc5847c4d…a65c

0x34b655…2a6f

12 touches
15 conflicts

0x5fde4971…aac9

0x34b655…2a6f

8 touches
6 conflicts

0x73c6bbd3…9969

0x34b655…2a6f

8 touches
6 conflicts

0x6ca0994e…02ef

0x34b655…2a6f

8 touches
6 conflicts

0x61bf2d7f…38f1

0x34b655…2a6f

8 touches
6 conflicts

0xd5b8ea71…af60

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

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 0xc5847c4d32…49a65c

← previous block·next block →recent activity