← previous blocknext block →recent activity

Analyzing

Block #102,231,692

19 transactions · 16 stateful · 2026-09-05 16:26:11 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,231,692  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x65c77c28…1a54

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x36d57732…26f7

0x34b655…2a6f

4 touches
1 conflict

0x3b25d07f…1dee

0x34b655…2a6f

4 touches
1 conflict

0x4321ddb0…ca88

0x34b655…2a6f

4 touches
1 conflict

0x4a70f78c…d41a

0x34b655…2a6f

4 touches
1 conflict

0x4f3cc09a…2804

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity