← previous blocknext block →recent activity
Analyzing
Block #79,241,281
18 transactions · 15 stateful · 2026-06-05 07:34:27 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #79,241,281 · 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
2w03w14w25w311w414w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e20cccf…19cc
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x52d65d97…1c96
0xa6afd3…d132
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x40970e69…da50
0x69df8a…6292
6 touches
3 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
6 touches
3 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 0x9e20cccfee…8c19cc
Audit this contract →
← previous block·next block →recent activity