← previous blocknext block →recent activity

Analyzing

Block #102,874,062

27 transactions · 25 stateful · 2026-09-07 22:35:48 UTC

Parallelism

93/100

Blocked

20%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #102,874,062  ·  27 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

0xb6ed511f…6b68

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x842d26a2…6006

0x34b655…2a6f

4 touches
1 conflict

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0x3243e72f…1f6d

0x34b655…2a6f

4 touches
1 conflict

0x6c820a19…d7a7

0x34b655…2a6f

2 touches
0 conflicts

0xa897aee4…51f5

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 0xb6ed511f4c…ab6b68

← previous block·next block →recent activity