← previous blocknext block →recent activity

Analyzing

Block #98,017,803

20 transactions · 18 stateful · 2026-08-21 21:47:38 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,017,803  ·  20 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

0xd541a808…4002

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xb8dc136f…fb16

0xc8689a…ee79

6 touches
3 conflicts

0x0c2c1966…1f92

0x34b655…2a6f

4 touches
1 conflict

0x3093e806…bde2

0x34b655…2a6f

4 touches
1 conflict

0x368833ad…2f8b

0x34b655…2a6f

4 touches
1 conflict

0x4158a962…db72

0x34b655…2a6f

4 touches
1 conflict

0x56755b2b…8d44

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 0xd541a8081f…994002

← previous block·next block →recent activity