← previous blocknext block →recent activity

Analyzing

Block #102,551,542

18 transactions · 17 stateful · 2026-09-06 19:27:12 UTC

Parallelism

83/100

Blocked

41%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,551,542  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x67d846dd…358c

0xfabe4b…7777

6 touches
3 conflicts

0x12a9b76e…cb76

0x3bd359…433a

6 touches
3 conflicts

0x44ed742f…63f5

0x3bd359…433a

6 touches
3 conflicts

0x4eb758b8…b13b

0x3bd359…433a

6 touches
3 conflicts

0x7cf5136f…ba69

0x9f3832…4ae4

6 touches
3 conflicts

0xa74647c3…ce06

0x9f3832…4ae4

6 touches
3 conflicts

0xa74647c3…ce07

0x9f3832…4ae4

6 touches
3 conflicts

0xcee2d213…c5cf

0x9f3832…4ae4

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: 0xfabe4b65…a27777

3 conflicts on slot 0x67d846dda0…aa358c

← previous block·next block →recent activity