← previous blocknext block →recent activity

Analyzing

Block #74,344,812

16 transactions · 14 stateful · 2026-05-13 15:11:22 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,344,812  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…0002

0xab3526…fa38

12 touches
15 conflicts

0x76c8341d…6678

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x2fb6ddd2…b2a4

0x000000…012a

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x12530975…a089

0x3bd359…433a

2 touches
0 conflicts

0x264c6e4e…cbb6

0x3bd359…433a

2 touches
0 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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity