← previous blocknext block →recent activity

Analyzing

Block #105,539,343

17 transactions · 15 stateful · 2026-09-17 06:56:01 UTC

Parallelism

88/100

Blocked

20%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #105,539,343  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x513b0c80…d2d9

0x34b655…2a6f

4 touches
1 conflict

0xf63c2a2b…bc5f

0x34b655…2a6f

4 touches
1 conflict

0xf63c2a2b…bc60

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x837b0792…3b9e

0x34b655…2a6f

4 touches
1 conflict

0x107b89e4…470d

0x34b655…2a6f

4 touches
1 conflict

0x34d95d94…3a16

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity