← previous blocknext block →recent activity
Analyzing
Block #79,241,166
36 transactions · 27 stateful · 2026-06-05 07:33:41 UTC
Parallelism
78/100
Blocked
63%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #79,241,166 · 36 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w111w012w113w215w016w117w218w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x685dbc3d…4313
0xd32edf…ff58
13 touches
21 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0xcdc8b4bb…7bce
0x34b655…2a6f
8 touches
6 conflicts
0x55b6a001…1e7a
0x34b655…2a6f
8 touches
6 conflicts
0x7cbd466f…1700
0x34b655…2a6f
8 touches
6 conflicts
0xaa0d0542…d8ec
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
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: Perpl
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity