← previous blocknext block →recent activity

Analyzing

Block #104,033,848

19 transactions · 17 stateful · 2026-09-12 00:06:28 UTC

Parallelism

74/100

Blocked

35%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #104,033,848  ·  19 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

0xb575cf74…fbd5

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x23a320fb…cbd7

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4929ad5d…ee56

0x34b655…2a6f

4 touches
1 conflict

0x736b9166…5ea5

0x34b655…2a6f

4 touches
1 conflict

0x81ca8c9e…28cb

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

6 conflicts on slot 0xb575cf748f…befbd5

← previous block·next block →recent activity