← previous blocknext block →recent activity
Analyzing
Block #79,122,742
44 transactions · 32 stateful · 2026-06-04 18:24:07 UTC
Parallelism
80/100
Blocked
69%
Avg conflicts / tx
1.73
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #79,122,742 · 44 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w48w59w610w716w317w518w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xdb95e18e…c738
0x1b6862…e19c
16 touches
28 conflicts
0xbd3bddcd…ada1
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0019
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0029
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 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: Perpl
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity