← previous blocknext block →recent activity

Analyzing

Block #94,847,110

18 transactions · 16 stateful · 2026-08-10 18:30:00 UTC

Parallelism

72/100

Blocked

38%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,847,110  ·  18 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

0x2b5101ac…090b

0x34b655…2a6f

8 touches
6 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xa4f80979…4d71

0x065c9d…c394

4 touches
1 conflict

0xd35bb5ac…3586

0x065c9d…c394

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x59dccbd8…2bf6

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

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 0x2b5101acd1…7c090b

← previous block·next block →recent activity