← previous blocknext block →recent activity

Analyzing

Block #93,371,033

18 transactions · 17 stateful · 2026-08-05 14:29:12 UTC

Parallelism

72/100

Blocked

41%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,371,033  ·  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

0x00000000…004b

0x80c745…7210

6 touches
3 conflicts

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x0468d641…be06

0x34b655…2a6f

4 touches
1 conflict

0x23253ea8…e0a4

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x4acbdbcf…a8c6

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: 0x80c74517…647210

3 conflicts on slot 0x0000000000…00004b

← previous block·next block →recent activity