← previous blocknext block →recent activity

Analyzing

Block #95,267,795

17 transactions · 16 stateful · 2026-08-12 05:55:34 UTC

Parallelism

59/100

Blocked

56%

Avg conflicts / tx

1.29

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,267,795  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0a57a2b8…3cdd

0x34b655…2a6f

12 touches
15 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x2b54cadb…4425

0xd18b7e…414b

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6bf457e3…9576

0x34b655…2a6f

4 touches
1 conflict

0x9068a9bc…86ee

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

15 conflicts on slot 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity