← previous blocknext block →recent activity
Analyzing
Block #79,241,245
28 transactions · 23 stateful · 2026-06-05 07:34:13 UTC
Parallelism
82/100
Blocked
39%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #79,241,245 · 28 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
1w06w07w18w29w310w416w420w123w024w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x9e20cccf…19cc
0xa6afd3…d132
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xdb067026…9eb8
0x69df8a…6292
8 touches
6 conflicts
0x565818b0…80a3
0xa6afd3…d132
8 touches
6 conflicts
0x40970e69…da50
0x69df8a…6292
8 touches
6 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
8 touches
6 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
8 touches
6 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: 0xa6afd386…b0d132
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity